update
This commit is contained in:
@@ -1,15 +1,22 @@
|
||||
The numbered entries below all describe the SAME block for the topic "{topic}". Entry number {current} was chosen as the canonical title. Check whether that is the best choice — if another entry is a clearly better canonical name, pick it instead.
|
||||
The numbered entries below all describe the SAME block for the topic "{topic}".
|
||||
|
||||
CURRENT TITLE: {current_title}
|
||||
|
||||
MEMBERS:
|
||||
{members}
|
||||
|
||||
Check whether the current title is the best canonical name for this block.
|
||||
|
||||
Rules:
|
||||
- Pick an EXISTING entry number — do NOT invent a title.
|
||||
- Best = most concrete, precise, self-explanatory, established term for the shared concept.
|
||||
- If the current choice ({current}) is already the best, return it unchanged.
|
||||
- When in doubt, keep the current choice.
|
||||
- Current title good (concrete, precise, self-explanatory, no reference/placeholder like "Satz 7.18") → confirm it.
|
||||
- Otherwise pick the best member ("best" REQUIRED) and optionally propose a SHORTER name: max 8 words, ONLY terms that appear in the members, exactly as concrete as the shared content — never a broader umbrella term, never a textbook concept the members don't mention. NO catalog/reference brackets ("(Satz 6.33)"); a known acronym in brackets ("(VC)") is fine.
|
||||
- When in doubt, confirm the current title.
|
||||
|
||||
Write ONLY the JSON file to: {out_path}
|
||||
Reply with ONLY the JSON — no code fences, no other text.
|
||||
|
||||
Format (the best member number, nothing else):
|
||||
{{"best": {current}}}
|
||||
Format:
|
||||
{{"ok": true}}
|
||||
or
|
||||
{{"best": 2}}
|
||||
or
|
||||
{{"best": 2, "name": "Kurzer kanonischer Titel"}}
|
||||
|
||||
Reference in New Issue
Block a user