Our few-shot examples came from the eval set. The 0.94 was fiction.
Article summary
Quick briefing — cleaned from the original RSS feed
TL;DR. Our ticket-routing eval scored 0.94 for five weeks. The number was manufactured. We had built a dynamic few-shot selector that retrieved the eight nearest labeled examples for each input, and we built its index out of the same labeled_tickets.jsonl the eval set was sampled from. So for every eval case, the nearest neighbor in that index was the eval case itself, gold label attached, pasted into the prompt directly above the question we were about to ask. The model was not answering. It…
1Key Takeaways
- Our ticket-routing eval scored 0.94 for five weeks.
- We had built a dynamic few-shot selector that retrieved the eight nearest labeled examples for each input, and we built its index out of the same labeled_tickets.jsonl the eval set was sampled from.
- So for every eval case, the nearest neighbor in that index was the eval case itself, gold label attached, pasted into the prompt directly above the question we were about to ask.
2AIWedia Score
8.1/10
High relevance — worth your attention today
Based on source trust, recency, category impact, and story depth.
3Why it matters
Coding AI shifts how fast software ships and how much human review each change needs. DEV — ML reports that our ticket-routing eval scored 0.94 for five weeks.
Explore related
Browse toolsCoding AI news
Explore curated coding ai tools on AIWedia — compare, rank, and launch from our directory.
Full story on DEV — ML
Read full articleHeadlines aggregated via RSS for discovery on AIWedia. Original content © DEV — ML. We link to the source and do not republish full articles.