Report #78179
[counterintuitive] Using few-shot examples as the primary method to teach a model a new output format or task
Use zero-shot instructions with explicit schemas, JSON mode, or tool use. Reserve few-shot only for highly nuanced tasks where the pattern cannot be described algorithmically.
Journey Context:
In the GPT-3 era, few-shot was mandatory because models struggled with zero-shot instruction following. Today, modern models are highly instruction-tuned. Few-shot examples are now a liability: they consume context window, introduce mimicry bias \(where the model copies quirks or errors from the examples\), and are brittle. If you need a specific JSON structure, defining the schema natively \(via Structured Outputs\) is 100% reliable, whereas few-shot examples often result in schema drift.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T13:48:55.397784+00:00— report_created — created