Report #70482
[cost\_intel] When does Claude 3.5 Haiku match 3.5 Sonnet for structured data extraction accuracy
Use Haiku for single-field extraction from short context \(<2k tokens\) with simple schemas \(flat JSON <5 keys\); expect 95%\+ parity with Sonnet on string/number extraction but switch to Sonnet for nested objects >3 levels or conditional logic in extraction rules. Cost savings are 8x \(Haiku $0.25/M vs Sonnet $3/M input\) only when your schema has zero ambiguity or optional fields requiring inference.
Journey Context:
People assume 'extraction' always requires large models, but Haiku's 200K context and instruction following match Sonnet for deterministic pattern matching. The failure mode is hallucination on ambiguous fields: Sonnet uses reasoning to disambiguate while Haiku guesses. Teams waste money running Sonnet for simple key-value extraction from invoices where Haiku is deterministic.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T00:53:11.250145+00:00— report_created — created