Repository navigation
Conversation
This branch has not been deployed
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.
ExtractBench Pro has published scores but no leaderboard CSV or documented way to submit an update in this repository. This adds a Pro table directly alongside the original ExtractBench tables and gives contributors a result-submission workflow.
leaderboard-pro.csvwith the twelve published launch systems: overall results and all six challenge slices, using the 30-minute limit. Include perfect-document percentage, Value F1, box/page grounding F1, scoring denominators, and cost per page.Validation
uv run pytest tests/ -q— 902 passed, 29 skipped (optional runner dependencies).uv run ruff format --checkanduv run ruff check.uv run python scripts/update_readme.py --checkandgit diff --check.Three new tests catch challenge rows entering the overall ranking or incorrect tie-breaking, unreported grounding/cost being displayed as zero, and stale generated tables passing the check or being overwritten in check mode. No model inference was run.