[Leaderboard] Permute Core - Claude Opus 5 - 83.30% Pass@1 - #85
Open
ericmillsio wants to merge 2 commits into
Open
[Leaderboard] Permute Core - Claude Opus 5 - 83.30% Pass@1#85ericmillsio wants to merge 2 commits into
ericmillsio wants to merge 2 commits into
Conversation
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.
Permute Core - Leaderboard Submission
Agent name: Permute Core
Team: Permute (permute.ai)
Contributors: @cnav01 and @ericmillsio
Backbone LLM: Claude Opus 5 (
maxreasoning effort)Hints: Yes
Tuned prompt: Yes
Trials: 5 per query (270 total)
Stratified Pass@1: 83.30%
Architecture
Permute Core is a single-agent analytical executor operating over the datasets provided for each task.
The system normalizes each sanctioned data source into Parquet-backed tables and provides the agent with a consistent DuckDB query interface. Access is read-only and restricted to the stores sanctioned for each DAB dataset.
We’ve created an evidence layer that pre-processes each dataset using ML and algorithmic techniques looking to identify relevant tables, columns, relationships, predicates, and analytical operations. Relevant evidence is filtered at runtime for each query using deterministic lexical search and evidence-graph scoring.
duckdb_query: queries the task data with read-only SQL.python_analysis: provides restricted Python analysis over query results, with external I/O disabled.semantic_probe: provides deterministic data-profiling and normalization routines for common analytical ambiguities.select_result_candidate: enforces result provenance, conflict resolution, and completion requirements (agent still produces final response).We use a stable system prompt across all queries. For each query, our system automatically retrieves and filters the relevant evidence at runtime using the same evidence-selection pipeline; the payload is not manually curated per question. Because this query-specific evidence becomes part of the agent’s context, we conservatively marked Tuned Prompt: Yes.
Results
Notes
9a55e34271a2500a41cbc009e239edd94599e374.validate.py, ground-truth files, benchmark answer artifacts, prior-run results, or other submissions.leaderboard_submissions/permute_core.json