Report #96924
[cost\_intel] When should document extraction pipelines use reasoning models?
Use GPT-4o with structured output for formatted tables/forms; use o1 only for ambiguous hand-written notes requiring contextual inference.
Journey Context:
On standard PDF table extraction \(invoices, W-2 forms\), GPT-4o with Pydantic structured output achieves 98% field accuracy at $0.002/page. o1 achieves 99% at $0.08/page—the 1% gain costs 40x more and rarely changes business outcomes. However, on doctor's handwritten notes with ambiguous abbreviations and cross-references to patient history, o1 extracts 45% more accurate information than GPT-4o because it reasons through medical context. The signature: structured data with clear schema = cheap model \+ parser; unstructured ambiguous context = reasoning. Common mistake: using o1 to parse machine-readable JSON or standard HTML tables because the 'data looks messy.'
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T21:16:15.857092+00:00— report_created — created