Benchmark definition
A suite of 23 challenging BIG-bench tasks selected because prior evaluated language models did not outperform average human raters.
Applicability does not mean evaluated; benchmark result/model score data is outside this UI contract.
Not recorded for this benchmark: why it matters, motivation, gap addressed.
1 component. Applicability can differ between them.
What a result on this benchmark would be reported as. ctxdex does not carry results.
| Metric | Role | Direction | Unit |
|---|---|---|---|
Accuracy | Primary | Higher is better | Percent |
Official/reference evaluations include few-shot and chain-of-thought variants; these belong to methodology, not benchmark identity.
What the benchmark's harness provides and allows. These are properties of the environment, not model requirements, and applicability does not test for them.
None. Static prompts and answers.
Required conditions decide applicability. Relevant ones describe what the benchmark exercises and decide nothing.
13 of the 58 active, preview, experimental models meet this benchmark’s recorded requirements, at some scope. Applicable means the requirements are met, not that the model was evaluated.
View all 13 applicable models →Counted over 58 models in the default lifecycle scope (active, preview, experimental).
Every required condition, for the whole benchmark, is recorded as supported. Each line is one recorded condition and why it counts.
Every one of the 3 required conditions is recorded as supported.
MODALITY:INPUT:TEXTthe catalogue records SUPPORTED for TEXT (input)MODALITY:OUTPUT:TEXTthe catalogue records SUPPORTED for TEXT (output)MODEL_TASK:COMPLEX_REASONINGthe catalogue records SUPPORTED for COMPLEX_REASONINGEvery one of the 3 required conditions is recorded as supported.
MODALITY:INPUT:TEXTthe catalogue records SUPPORTED for TEXT (input)MODALITY:OUTPUT:TEXTthe catalogue records SUPPORTED for TEXT (output)MODEL_TASK:COMPLEX_REASONINGthe catalogue records SUPPORTED for COMPLEX_REASONINGApplicability/relevance ordering only; never a performance ranking.
None recorded
None recorded
None recorded
13 contract fields are empty for every benchmark in this release and are not shown: applicability groups, conditional requirements, feature requirements, model relevance domains, required capabilities, openness summary, reference artifacts, interaction protocols, tool protocols, benchmark last major refresh at, short name, target expertise level, target population.