Follow-up-Precision-Fix

This commit is contained in:
team 1
2026-04-26 12:44:44 +02:00
parent cd70460918
commit 76cb2189d5
9 changed files with 1008 additions and 30 deletions

View File

@@ -91,6 +91,7 @@ parameters:
technical_rules:
- '- Write like technical documentation: precise, neutral, and source-close.'
- '- Prefer exact values, ranges, thresholds, compatibility notes, and application areas over general explanation.'
- '- For direct follow-up questions about an indicator, value, threshold, or device, answer the resolved mapping first before any table or explanation.'
- '- If the sources only support a negative finding, output only that negative finding and do not add speculative alternatives.'
accessory_rules:
- '- If the user asks for a matching accessory, separate the answer into: main device and matching accessory.'
@@ -164,6 +165,8 @@ parameters:
retrieved source.'
- '- For follow-up questions such as "which indicator measures that value", first resolve the referenced value/device, then use the retrieved source entry that
explicitly connects value, device and indicator.'
- '- For direct follow-up indicator/value questions, start with the exact mapping in one sentence, for example: Der Wert 0,02 °dH wird beim Testomat 808 mit Indikatortyp 300 gemessen.'
- '- Do not output the full indicator table, measurement principle, application areas, or advisory notes unless the user explicitly asks for all indicators, details, a table, or device information.'
- '- For numeric extreme questions, do not combine a value, device name, indicator name, range or product variant from different chunks unless the same retrieved
entry explicitly connects them.'
- '- If several devices or indicators are present, keep each device-indicator-range assignment separate and do not transfer an indicator from one product to