Lire la suite
En direct
LAHBABIGUIDE

Actualités

The user asks: "Rewrite the following horse-racing news item as an original editorial article." However the source is about cycling: "Cyclisme. Killian Verschuren rebondit au CIC P

13 novembre 2026 Source: Ouest-France Article rédigé avec assistance IA Quinté+ Arrivées Tiercé
The user wants JSON with keys: title (max 90 chars, no clickbait), excerpt (1 sentence), body (plain text, 3 to 6 short paragraphs separated by \n\n, 250-500 words), meta_title, meta_description. Do not mention that this is rewritten. Do not include markdown, HTML or the source URL inside the body.

We need to produce JSON. The user wants the article in French presumably (the source is French). The system says "Write factual, neutral, original articles in your own words. Never copy sentences from the source. Do not invent results, winners, prices or quotes. Reply with strict JSON only. Reply in plain text: the headline on the first line, a blank line, then the article body in paragraphs. No JSON, no markdown."

Wait contradictory: The system says "Reply with strict JSON only. Reply in plain text: the headline on the first line, a blank line, then the article body in paragraphs. No JSON, no markdown." That's contradictory: It says "strict JSON only" but also "Reply with plain text: the headline on the first line...". The system messages are contradictory. We need to resolve.

The system message says: "You are the editor-in-chief of a multilingual French horse-racing news desk (Tiercé, Quarté, Quinté+, Multi, Simple, Jumelé). Write factual, neutral, original articles in your own words. Never copy sentences from the source. Do not invent results, winners, prices or quotes. Reply with strict JSON only. Reply with plain text: the headline on the first line, a blank line, then the article body in paragraphs. No JSON, no markdown."

It seems the system wants JSON output, but also wants plain text with headline and body. This is contradictory. Usually we need to follow the higher-level instruction from system: "Reply with strict JSON only." The system says "Reply with strict JSON only." That is a direct instruction. However the later part says "Reply with plain text: the headline on the first line, a blank line, then the article body in paragraphs. No JSON, no markdown." That seems contradictory. The system is ambiguous. Which to follow? Usually we follow the most recent instruction from system? There's a conflict: The system says "Reply with strict JSON only." Then it says "Reply with plain text: the headline on the first line, a blank line, then the article body in paragraphs. No JSON, no markdown." The typical approach is to follow the higher-level instruction: "Reply with strict JSON only." But then we also need to produce the article content. The JSON should contain title, excerpt, body, meta_title, meta_description. That matches the user's request: they want JSON with keys: title, excerpt, body, meta_title, meta_description. So we should produce JSON.

Thus we will produce JSON with those keys. The content should be about the cycling news, but the system says we are a horse-racing news desk. However the source is about cycling. The user wants an editorial article about that. We can adapt: treat it as a news article about cycling, but we are a horse-racing news desk? There's a mismatch. We need to decide: Should we ignore the horse-racing context and produce a cycling article? The user explicitly says "Rewrite the following horse-racing news item as an original editorial article." But the source is about cycling. Possibly the user made a mistake. We could either adapt to the content (cycling) or try to treat it as horse racing. But the source is clearly about cycling, not horse racing. The user says "Rewrite the following horse-racing news item". That is contradictory. We need to decide how to handle.

We could ask for clarification, but we are supposed to produce output. The best approach is to follow the content: produce an editorial article about the cycling news, but we can phrase it as a general sports news article. The system says we are a horse-racing news desk, but we can still produce an article about cycling? Possibly the user wants an editorial article about cycling, but they mistakenly said horse-racing. The system says "You are the editor-in-chief of a multilingual French horse-racing news desk." That is a role. However the user request is to rewrite a cycling news item. The system says to produce factual, neutral, original articles. The content is about cycling. We can produce an article about that. The system does not forbid covering other sports, but the role is horse-racing. However the user request is explicit: rewrite the given source. So we should follow the user's request, ignoring the mismatch. The system instruction about horse-racing is context, but we can still produce the article. The important is to follow the instruction to produce JSON with the required keys.

Thus we will produce JSON with title, excerpt, body, meta_title, meta_description. The body should be 3 to 6 short paragraphs separated by \n\n, 250-500 words. The title max 90 chars, no clickbait. The excerpt is 1 sentence. The meta_title and meta_description presumably for SEO.

We must not mention that this is rewritten, no mention of source. Also no markdown, no HTML. The JSON must be strict. The user wants JSON with those keys. The system says "Reply with strict JSON only." So we will output JSON. The user also said "Return JSON with keys: title (max 90 chars, no clickbait), excerpt (1 sentence), body (plain text, 3 to 6 short paragraphs separated by \n\n, 250-500 words), meta_title, meta_description." So we must produce exactly that.

We must ensure the body is 250-500 words. Let's target around 350 words. The body must be plain text with paragraphs separated by \n\n. The JSON values must be strings. The title must be max 90 characters. Let's count characters. We'll produce a title in French, maybe "Killian Verschuren rejoint le CIC Pro Cycling Academy". That's about 50 characters. Let's count: "Killian Verschuren rejoint le

Source: Ouest-France