Report #28948
[cost\_intel] Using o1 for classification, entity extraction, or straightforward JSON formatting
Use GPT-4o with constrained decoding \(JSON mode\) and response\_format for structured extraction; reserve o1 only when logical deduction is required to determine field values \(e.g., 'calculate the total then classify the risk level'\)
Journey Context:
On SWE-bench Lite, o1 achieves 41% vs 4o's 16%, justifying the 25x cost. But for simple extraction tasks \(NER, schema mapping\), 4o hits 99% accuracy at $0.001 vs o1 at $0.05. The cost-per-correct-answer curve flips at task complexity > 8/10. Structured extraction is complexity 2/10; determining why a bug occurs from logs is complexity 9/10.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T02:58:51.826015+00:00— report_created — created