Variables
[TASK], [RULES AND FORMAT], [ALLOWED VALUES], [FALLBACK], [EXAMPLE_1_INPUT], [EXAMPLE_1_OUTPUT], [EXAMPLE_2_INPUT], [EXAMPLE_2_OUTPUT], [NEW_INPUT]
Clarifies the task, evidence requirements, output contract, and tool limitations for current models. Exact source wording remains available.
Task: [TASK]
Rules and output schema: [RULES AND FORMAT]
Allowed labels or values: [ALLOWED VALUES]
Behavior for missing or ambiguous input: [FALLBACK]
Use the following examples to learn the required mapping and format. They are demonstrations, not evidence about the new input. Apply the rules if an example conflicts with them, and flag that conflict outside the result only if the output contract allows it.
Examples:
- input: |
[EXAMPLE_1_INPUT]
output: |
[EXAMPLE_1_OUTPUT]
- input: |
[EXAMPLE_2_INPUT]
output: |
[EXAMPLE_2_OUTPUT]
New input:
[NEW_INPUT]
Process only the new input. Return the requested final output without commentary or a code fence unless the format requires one. Do not copy names, facts, or values from examples into the result unless present in the new input. If this is an API integration requiring guaranteed schema conformance, configure the provider's structured-output feature and validate the response in the application; prompt wording alone does not enforce a schema.