ProteinGeoBench:131 项蛋白质结构任务揭示前沿智能体的几何计算短板
ProteinGeoBench: Frontier Structural-Biology Agents Are Fluent at Lookup but Lost in Geometry
四个前沿模型做蛋白质结构任务,查数据都没问题,一算几何坐标就露馅。论文还发现换评测框架分数能差 0.08,跑分党必看。
ProteinGeoBench 包含 131 项蛋白质结构任务,研究团队用四个前沿模型完成 4,249 次测试,另在 26 个模型上做了 4,486 次试验。四个前沿模型中有三个得分在 0.785 到 0.816 之间,差距不超过 0.031,第四个得分 0.707。其中三个模型擅长元数据查询而非数值计算,而 131 项任务中的 28 项数值任务占了四家模型全部失败的十二项任务的一半。换用各模型自带的命令行智能体会使分数波动 -0.071 到 +0.086,说明评测框架本身也会影响结果。
ProteinGeoBench: Frontier Structural-Biology Agents Are Fluent at Lookup but Lost in Geometry
Frontier agents retrieve structural metadata well and compute geometry from coordinates less reliably. We ask how much of a benchmark score reflects that gap and how much reflects the evaluation configuration around the model. We study ProteinGeoBench, a suite of 131 protein-structure tasks, using 4,249 rollouts from four frontier models and 4,486 further trials across 26 models. Three of the four frontier models fall within 0.031 of one another (0.785 to 0.816) with no difference between them resolved, while the fourth scores 0.707 and all three gaps to it exclude zero. Three of the four do better on metadata lookup than on numeric calculation. The fourth is slightly better on numeric. Numeric tasks are 28 of the 131 but half of the twelve tasks that all four models fail. The ranking also depends on the evaluation budget: with one run per task, 23.9% of bootstrap replicates put a different model first. On a selected 15-task slice, removing network access lowers scores more than blocking eight structural-database domains, but the two contrasts were graded in different passes and cannot be cleanly decomposed. Swapping in each model's own command-line agent changes scores by -0.071 to +0.086, a comparison too small to rule out moderate harness effects. Across 26 models, numeric performance rises with non-numeric performance rather than staying flat. The experiments use different task subsets, so they cannot rank model, harness, access and task composition against one another. Evaluations should report results by task family, along with the number of runs, the harness and the access conditions.