Report #62461
[cost\_intel] Using o1-preview for strict JSON schema extraction resulting in 5% syntax error rate vs 0.1% for GPT-4o strict mode
Use GPT-4o with Structured Outputs \(strict JSON mode\) or Zod schemas for any extraction requiring 100% schema adherence; reserve o1/o3 for reasoning-heavy extraction where output structure is secondary to inference depth, then sanitize output through GPT-4o-mini for formatting.
Journey Context:
o1-preview lacks 'strict mode' and generates reasoning tokens that occasionally violate JSON syntax \(unescaped quotes, trailing commas\). GPT-4o with response\_format=\{'type': 'json\_schema'\} enforces grammar at the token sampler level. The degradation signature is parsing failures on nested objects. For complex reasoning extraction \(e.g., 'extract the logical fallacy type'\), use o1 for analysis then 4o-mini for JSON packaging.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T11:19:25.895973+00:00— report_created — created