docs: publish GPT-OSS GPQA-main pruning results - #36
Merged
HectorHHZ merged 1 commit intoSep 21, 2026
Merged
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.
What and why
This PR publishes the completed GPT-OSS-120B held-out GPQA-main comparison after pruning on the same 64-example GPQA-main calibration split. It also teaches the frozen evaluator to preserve
gpqa_mainas a distinct dataset configuration instead of labeling everyIdavidrein/gpqamanifest as Diamond.Each model completed 384 held-out questions × 8 independent samples, or 3,072 completions. The metric is mean pass@1 over all completions; unparsed answers count as incorrect. All four runs have zero length truncations.
The exact 64-row calibration and 384-row held-out split is linked at
jayzou3773/less-is-moe-gpqa-main-calibration-64, revision7134dfef5af4605eae0706c30efa9226f49aed96. The dataset remains access-controlled because GPQA asks users not to reveal examples online.The artifact directory contains complete metrics, run settings, grading audits, and all 12,288 per-sample predictions. Public predictions are sanitized: they retain UUIDs, gold/predicted letters, correctness, finish status, token counts, and question hashes while omitting question text, options, answer text, raw generations, and final-answer prose. The artifact manifest records SHA-256 hashes for the private raw and graded prediction files.
This is stacked on #35 because the experiment record follows the GPQA artifact format introduced there, and #35 is stacked on the evaluator in #34. After those PRs merge, this branch can be retargeted to
mainwithout changing this commit.Verification
uv run --with pytest --python 3.12 python -m pytest -q tests/test_supergpqa.py tests/test_registry_and_protocols.py— 28 passedgpqa_mainlabels, exact correct/unparsed/token sums, and absence of restricted fieldsartifact-manifest.jsonSHA-256 valuespython3 -m json.toolon the experiment record, artifact manifest, and split manifestgit diff --cached --checkAI assistance
Codex collected the frozen B200 outputs, generated question-safe prediction artifacts, added explicit GPQA-main routing, wrote the experiment records, and performed consistency and privacy checks. Model generations and grading values come from the recorded B200 runs.
Checklist
pytestpasses for the affected evaluator and registry tests.