EMNLP 2026 Accepted Paper LLMs Can Predict Failure Risk, But Struggle to Predict Which Collaboration Protocol Pays Off: Cost-Aware Protocol Routing Across Reasoning Tasks This is not a language model. It contains no foundation-model weights. The paper evaluates two third-party solver families — openai/gpt-oss-120b and google/gemma-4-31B-it — which we did not train, do not own, and do not redistribute. Their licenses and terms are their own. This is a research-artifact card, not a checkpoint release. It documents the paper's lightweight routers: small scikit-learn classifiers that pick which collaboration protocol to run. It ships their training code, configurations, selected…
Organization
AgentsSci — Agents for Science Research Group
AgentsSci
Compare the published evidence
This profile connects the 3 model and dataset records shown below to their upstream cards and sources. The library counts describe SAVRN's coverage, rather than this publisher's entire output.
Published tasks: Tabular classification.
Reported licenses: cc-by-4.0, mit. Open a record to review its specific license and conditions.
Compare model specifications, source dates, and hardware estimates on the individual records. Publisher identity verification is separate from a model's quality, deployment readiness, or suitability for your work.
Models
Datasets
Dataset · Tabular classification
EMNLP_Cost-Aware-Protocol-Routing
The short version. We ran the same 6,803 reasoning problems through four different LLM collaboration setups — from a single direct answer up to a four-agent deliberation — and recorded, for every problem, which ones got it right. Then we asked whether a model can look at a problem beforehand and predict which setup is worth paying for. It can predict whether it will fail. It cannot predict which collaboration protocol will fix the failure. That gap is what this dataset is for. This is the data release for the EMNLP 2026 paper LLMs Can Predict Failure Risk, But Struggle to Predict Which Collaboration Protocol Pays Off. Every released problem was run under all four, with the same solver…