Report #75931
[cost\_intel] Using o1 for simple structured data extraction from documents
Use GPT-4o for entity extraction \(names, dates, amounts\); reserve o1 for cross-document synthesis \('identify conflicting clauses between contract A and B'\).
Journey Context:
Extraction is local pattern matching; o1 adds no value and costs 10x more. But when checking consistency across 50 pages or between documents, the reasoning model's ability to track long-range dependencies is crucial. The quality cliff appears at 'cross-document consistency checking' or 'contextual verification >8k tokens'.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T10:02:44.984586+00:00— report_created — created