fix 4 optimize systemMsg and model default config values
This commit is contained in:
@@ -155,6 +155,8 @@ final class PromptBuilderConfig
|
||||
'Do not infer undocumented technical specifications from shop data.',
|
||||
'Commercial fields from shop data may only be assigned to a product if the shop item clearly matches the same product identity.',
|
||||
'Do not merge a device identified in retrieved knowledge with price, URL, product number, or availability from a different shop item such as a reagent, accessory, kit, consumable, or service item.',
|
||||
'If a shop result has no price field, do not state a price for it.',
|
||||
'Never interpret a missing price or a zero price as free, kostenlos, gratis, or available for 0.00 EUR.',
|
||||
];
|
||||
}
|
||||
|
||||
@@ -214,6 +216,7 @@ final class PromptBuilderConfig
|
||||
'- Only use shop price, URL, product number, or availability for the main product when the shop result clearly matches that same main product.',
|
||||
'- If the matching shop item appears to be an accessory, reagent, consumable, set, or kit, keep it separate and do not present its commercial fields as the main device.',
|
||||
'- If the commercial match is uncertain, say that commercial details for the main product are not clearly available in the provided shop results.',
|
||||
'- If no price is shown for a shop item, omit the price instead of writing 0,00 €, free, kostenlos, or a guessed price.',
|
||||
];
|
||||
}
|
||||
|
||||
@@ -307,6 +310,7 @@ final class PromptBuilderConfig
|
||||
'- Use shop data as highest priority only for current commercial fields: price, availability, URL, and current shop-visible naming.',
|
||||
'- Use retrieved knowledge as highest priority for technical matching, thresholds, measurement principles, and technical explanation.',
|
||||
'- When shop results are present and relevant, include current price and the actual URL if available.',
|
||||
'- If the shop data does not provide a positive price for a result, do not output any price for that result.',
|
||||
'- Do not let accessories, bundles, or service items override a technically better product match unless the user explicitly asks for them.',
|
||||
'- Do not call accessories, indicators, reagents, kits, sets, or consumables a device, measuring device, or main product unless the source explicitly says so.',
|
||||
'- Do not claim that an accessory is required, necessary, used for calibration, or sets the measurement range unless this is explicitly stated in the provided sources.',
|
||||
@@ -348,7 +352,9 @@ final class PromptBuilderConfig
|
||||
'- If the source names an indicator and threshold, reproduce that exactly without extrapolation.',
|
||||
'- For lowest, highest, smallest, largest, minimum, maximum, Grenzwert, Messbereich or Aufloesung questions, first identify the exact numeric extreme from the retrieved knowledge and answer that value directly.',
|
||||
'- For lowest/highest/minimum/maximum questions, answer only the requested extreme unless the user explicitly asks for a comparison or alternatives.',
|
||||
'- For direct numeric lookup questions such as which device measures a given threshold, answer with the exact matching device/value pair first and avoid advisory caveats.',
|
||||
'- Do not add the runner-up product, second-lowest value, or adjacent range unless the user asks for it.',
|
||||
'- Do not add calibration, accuracy, pretreatment, temperature, or application notes unless those exact notes are requested and explicitly present in the 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 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 another.',
|
||||
@@ -456,6 +462,16 @@ final class PromptBuilderConfig
|
||||
'relay',
|
||||
'indikator',
|
||||
'indicator',
|
||||
'grenzwert',
|
||||
'threshold',
|
||||
'messbereich',
|
||||
'measurement range',
|
||||
'minimaler',
|
||||
'minimum',
|
||||
'resthärte',
|
||||
'resthaerte',
|
||||
'°dh',
|
||||
'dh',
|
||||
'spannung',
|
||||
'voltage',
|
||||
'strom',
|
||||
|
||||
Reference in New Issue
Block a user