Report #93943
[counterintuitive] Providing 3-5 full examples \(few-shot\) to teach a model a new task format
Use zero-shot with clear structural schemas \(JSON/XML\) or tool definitions; only use few-shot if the task involves highly idiosyncratic stylistic nuances.
Journey Context:
Few-shot was essential for base models \(davinci\) to understand intent. Instruction-tuned models already understand 'Output JSON' or 'Summarize this.' Few-shot examples consume massive context windows, cost tokens, and often introduce bias or anchor the model too heavily to the specific examples, reducing its ability to generalize to edge cases not represented in the shots. Zero-shot with strict schema constraints is more robust and token-efficient.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T16:16:12.658183+00:00— report_created — created