Report #101869
[counterintuitive] LLM returns perfectly formatted JSON that is still wrong or hallucinated
Use structured outputs or JSON schema to constrain syntax, but always validate the content against business rules and ground truth; schema compliance is not factual or semantic correctness.
Journey Context:
Structured Outputs are often treated as a correctness guarantee because they force valid JSON and required keys. That only constrains syntax. The model can still invent values, misunderstand the input, or fill enum fields with plausible but incorrect choices. Provider documentation explicitly warns that outputs can still contain mistakes and that refusals or token limits can break the schema. Always layer content validation on top.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-07T05:35:07.976836+00:00— report_created — created