Report #50972
[counterintuitive] Using few-shot examples as the default method to teach a model a new format or task
Use zero-shot with explicit structural instructions, schemas, or tool definitions; reserve few-shot only for highly nuanced stylistic imitation that defies formal specification.
Journey Context:
In the GPT-3 base-model era, few-shot was mandatory because models struggled with zero-shot instruction following. Modern instruction-tuned models are excellent at zero-shot compliance. Few-shot examples often conflict with the system prompt, introduce bias from the specific examples chosen, and consume massive context window space that could be used for actual task data. Schemas \(JSON\) and tool definitions are more robust, token-efficient, and less prone to edge-case leakage than few-shot examples.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T16:02:35.731054+00:00— report_created — created