Lire la suite
En direct
LAHBABIGUIDE

Actualités

The user asks: "Rewrite the following horse-racing news item as an original editorial article." But the source is about tennis (Masters 1000 Paris, Alcaraz). The user wants a rewri

7 novembre 2026 Source: Ouest-France Article rédigé avec assistance IA Quinté+ Arrivées Tiercé Analyses
But then the user says: "Rewrite the following horse-racing news item as an original editorial article." Actually the source is tennis, not horse racing. There's a mismatch. The system instructions say to output JSON with keys: title, excerpt, body, meta_title, meta_description. However 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 to output JSON, but also says no JSON? Let's parse: The system says: "You are the editor-in-chief of a multilingual French horse-racing news desk ... 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."

This is contradictory: "Reply with strict JSON only." vs "Reply with plain text: the headline on the first line, a blank line, then the article body in paragraphs. No JSON, no markdown." So we need to resolve the conflict. The higher-level instruction: The user wants JSON with keys: title, excerpt, body, meta_title, meta_description. The system says "Reply with strict JSON only." So we must output JSON. The system also 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's contradictory. Usually we follow the system's higher-level instruction about format? The system says "Reply with strict JSON only." That's a direct instruction. The user also wants JSON. So we should output JSON. The system also says "Reply with plain text: the headline on the first line, a blank line, then the article body in paragraphs. No JSON, no markdown." This seems contradictory. Usually we interpret that the system says "Reply with strict JSON only." So we output JSON.

Thus we need to produce 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.

We need to rewrite the source about Alcaraz. The source is about tennis. However the system says we are a horse-racing news desk. But the user wants a rewrite of that article. There's a mismatch. Possibly we should treat it as a generic sports news article, maybe we can adapt it to horse racing? But the source is about tennis. There's no mention that we must adapt to horse racing. The system says we are a horse-racing news desk, but the user wants a rewrite of a tennis article. We could incorporate horse racing? Possibly we can rewrite the article as a horse-racing article, but that would be inventing content. The system says "Do not invent results, winners, prices or quotes." So we cannot invent a horse race. So we must rewrite the source as is, but we are a horse-racing news desk? That seems contradictory. Perhaps we can treat the article as generic sports news, not specifically horse racing. The system says we are a multilingual French horse-racing news desk, but we can still write about other sports? Usually a news desk might cover other sports but the system says "Tiercé, Quarté, Quinté+, Multi, Simple, Jumelé". Those are horse betting types. So maybe they only want horse racing. But the user gave a tennis article. Possibly the user made a mistake. We could ask for clarification, but we must respond. The system says to reply with JSON. We need to produce a rewrite of the tennis article, but we must not copy sentences. We can produce a new article summarizing the same facts: Alcaraz qualified for his first final at the Paris Masters 1000, beating Casper Ruud in two sets on November 7. We must not invent results, winners, prices or quotes. So we can only use the given facts. We must produce an editorial article (maybe with some analysis). But we must not invent quotes. We can produce a neutral factual article.

We need to produce a title, excerpt, body, meta_title, meta_description.

We must ensure the body is 250-500 words, 3 to 6 short paragraphs separated by \n\n. The body must be plain text. The JSON must have keys: title, excerpt, body, meta_title, meta_description. The title max 90 chars. The excerpt is 1 sentence. The meta_title maybe similar to title but maybe longer? Usually meta_title is for SEO, maybe same as title. The meta_description is a short description for SEO, maybe 150-160 chars. The user wants JSON.

Thus we need to produce JSON like:

{
"title": "...",
"excerpt": "...",
"body": "...",
"meta_title": "...",
"meta_description": "..."
}

We must ensure no markdown, no HTML. The body must be plain text with paragraphs separated by \n\n.

We must ensure we do not copy sentences from source. So we must rewrite in our own words.

We must also ensure we do not invent any results beyond the given. The source says Alcaraz beat Ruud in two sets. That's a fact. We can mention that. The source says it's his first final at the Masters 1000 in Paris. That's a fact. The date is November 7. We can mention that. The source says Alcaraz is world No. 3. That's a fact. We can mention that.

We must not mention the source URL. The user gave no URL. So fine.

We must ensure the body is 250-500 words. Let's aim for around 350 words. Provide 4 paragraphs.

We must ensure the excerpt is one sentence. Possibly "Carlos Alcaraz a atteint sa première finale du Masters

Source: Ouest-France