Benchmark definition
PIQA
A binary-choice benchmark for physical commonsense reasoning in natural language.
Applicability does not mean evaluated; benchmark result/model score data is outside this UI contract.
About
- Description
- PIQA asks models to choose the more physically plausible solution to everyday goals, targeting knowledge that is often underrepresented in text.
- What it measures
- Physical commonsense about objects, actions, and everyday interactions.
- Comparison guidance
- Not published
- Intended difficulty
- Not published
Not recorded for this benchmark: what it does not measure, why it matters, motivation, gap addressed.
Classification
- Categories
- Commonsense
- Domains
- Everyday / commonsense world
- Evaluation style
- Automatic reference matchStatic Q&A
Structure
One undivided item set. No components or scenarios recorded.
Tasks
None recorded
Metrics
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 |
Methodology
None recorded
Evaluation environment
What the benchmark's harness provides and allows. These are properties of the environment, not model requirements, and applicability does not test for them.
- Interaction
None. Static prompts and answers.
- Evaluation style
- Automatic reference match, Static Q&A
- Environment summary
- Not published
Model requirements
Required conditions decide applicability. Relevant ones describe what the benchmark exercises and decide nothing.
Required · decides applicability
Relevant · informational
CTXDEX models
1 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 1 applicable model →- Applicable · full
- 1
- Applicable · components
- 0
- Applicable · scenarios
- 0
- Conditionally applicable
- 0
- Not recorded
- 57
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:PHYSICAL_SCENE_REASONINGthe catalogue records SUPPORTED for PHYSICAL_SCENE_REASONING
Applicability/relevance ordering only; never a performance ranking.
Scale
None recorded
Data and access
- Dataset
- Open
- Evaluation code
- Open source
- Unknown
- Leaderboard, Peer review, Maintenance
Coverage
- Languages, regions
None recorded
- Coverage summary
- Not published
Limitations
None recorded
Lineage
- Family
None recorded
- Related
None recorded
- Changes
None recorded
Sources
- PIQA paper ↗Research paper · Original creator
- Official PIQA data page ↗Dataset · Benchmark official
Freshness
- Content version
- 1.0
- Last reviewed
- 2026-09-22
- Refresh model
- Static
- Time sensitivity
- Low
- Benchmark data
- c40cccac878af5d0
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.