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 handball, not horse racing. The user wants a rewrite as

13 novembre 2026 Source: Ouest-France Article rédigé avec assistance IA Quinté+ Arrivées Tiercé
But then the user says: "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. Do not mention that this is rewritten. Do not include markdown, HTML or the source URL inside the body."

So there is a conflict: The system message 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." But the user request says "Return JSON with keys: title, excerpt, body, meta_title, meta_description."

Which instruction takes precedence? According to instruction hierarchy: system > developer > user. 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: system says "strict JSON only" but also says "Reply in plain text: the headline on the first line, a blank line, then the article body in paragraphs." The system message is contradictory: It 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." This is contradictory: It says both JSON only and plain text. Usually the system message is higher priority than developer. But we have a conflict: The system says "Reply with strict JSON only." Then also says "Reply in plain text: the headline on the first line, a blank line, then the article body in paragraphs." This is contradictory. Which part is more specific? The system says "strict JSON only." The later part says "Reply in plain text: the headline on the first line, a blank line, then the article body in paragraphs." The instruction "strict JSON only" likely overrides the later part. But we also have a user request to return JSON with specific keys. So the user request aligns with system "strict JSON only". The system also says "Reply in plain text: the headline on the first line, a blank line, then the article body in paragraphs." That conflicts. Usually we should follow the higher-level instruction: "strict JSON only." So we should output JSON.

But we need to be careful: 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." This is contradictory. The system says "strict JSON only" but then says "Reply in plain text: the headline...". This is ambiguous. Possibly the system message is incorrectly formatted. In such ambiguous cases, we need to resolve the conflict. The system says "strict JSON only" which is a clear directive. The later part "Reply in plain text..." is contradictory. The "strict JSON only" is a higher-level directive. So we should follow that.

Thus we should produce JSON with keys: title, excerpt, body, meta_title, meta_description. The body should be plain text, 3 to 6 short paragraphs separated by \n\n, 250-500 words. The title max 90 chars. The excerpt is 1 sentence. The meta_title and meta_description presumably also short.

We must rewrite the source content as an original editorial article. The source is about handball, not horse racing. The user says "Rewrite the following horse-racing news item as an original editorial article." But the source is handball. Possibly they want to treat it as a horse-racing news item? Or they want to rewrite the handball article as a horse-racing article? The instruction 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." So we need to produce a horse-racing article, not handball. But the source is handball. There's a mismatch. We need to interpret the request: The user wants to rewrite the given source as an original editorial article. The source is about handball. But the system says we are a horse-racing news desk. So maybe we need to adapt the content to horse racing, i.e., treat the handball story as if it were a horse-racing story? Or we need to ignore the mismatch and rewrite the handball article as a horse-racing article, maybe by replacing the sport? The user says "Rewrite the following horse-racing news item as an original editorial article." But the source is handball. Possibly they made a mistake. The instruction says "You are the editor-in-chief of a multilingual French horse-racing news desk." So we should produce a horse-racing article. The source is about handball. We could adapt the story to horse racing: maybe the "Niort HB souchéen" is a horse racing team? But it's handball. We could reinterpret "Niort HB souchéen" as a horse racing stable? That would be weird. But we can treat the story as a horse racing context: maybe "Niort" is a stable, "Poitiers" is a race location, "victoires consécutives" is winning streak. But the original story is about handball. However, the user explicitly says "Rewrite the following horse-racing news item as an original editorial article." The source is handball. Possibly they want to treat it as a horse-racing article, but we need to adapt it to horse racing context. The instruction says "Write factual, neutral, original articles in your own words." So we can rewrite the content, but we need to ensure it's about horse racing. We can reinterpret "team" as "stable", "victories" as "wins", "match" as "race", "score" as "performance". But we must not invent results, winners, prices or quotes. The source says "Le Niort HB souchéen, qui reste sur trois victoires consécutives, espère poursuivre sa série ce

Source: Ouest-France