Report #43540
[counterintuitive] Enabling JSON mode or structured output prevents the model from hallucinating invalid data
Use structured output for format guarantees only. Independently validate all values — check that referenced files exist, that API names are real, that numerical values are in valid ranges. Schema validation is syntactic, not semantic.
Journey Context:
JSON mode and structured outputs constrain the token distribution to produce valid JSON matching a schema. Developers routinely conflate 'well-formed output' with 'correct output.' The model will produce perfectly valid JSON with completely fabricated values — hallucinated function names, invented file paths, plausible but wrong parameter values. The schema constraint ensures the output parses; it does nothing to ensure the content is grounded in reality. This is especially dangerous because well-formatted output feels more trustworthy, creating a false confidence that the structured output feature is doing more than syntax enforcement. The model's ability to satisfy a JSON schema and its ability to produce factually correct content are completely orthogonal capabilities.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T03:33:15.052532+00:00— report_created — created