Repository navigation
Record the live benchmark score: 29/30 - #10
Merged
Merged
Conversation
Routing 97%, filters 100%, answer checks 100%, median latency 2.6 s, all 30
answers written by the LLM. The remaining miss ("Profiles in the Bay of Bengal
in September 2026" routed to custom SQL) is noted in the README.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Records the benchmark result from the live API after #9 was deployed: 29/30 questions fully correct. Routing 97%, filters 100%, answer checks 100%, median latency 2.6 s, and all 30 answers written by the LLM.
Adds
eval/latest.md(per-question table) andeval/latest.json(raw results), and puts the score in the README.Known miss: "Profiles in the Bay of Bengal in September 2026" was routed to custom SQL instead of profile search. It passed in the first run, so the new count example in the router prompt may be pulling borderline "profiles…" questions toward SQL. This is left as is rather than tuning the benchmark until it passes.
🤖 Generated with Claude Code