Report #77807
[counterintuitive] adding more few-shot examples always improves performance
Use 3-5 highly diverse, high-quality few-shot examples. Avoid adding many similar examples, as it biases the model's output distribution toward the majority class in the examples rather than the actual task logic.
Journey Context:
Developers often dump 20\+ examples into a prompt thinking more is better. This causes the model to overfit to the specific phrasing of the examples \(label bias\) and wastes context window, increasing latency and cost. A few well-chosen, diverse examples that cover edge cases outperform a large batch of homogeneous ones.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T13:11:46.398205+00:00— report_created — created