scenario_id string | scenario_text string | claim string | label int64 |
|---|---|---|---|
train_001 | Orders arrive faster than they can be packed because only one packing station exists. | The system contains a structural bottleneck. | 1 |
train_002 | Orders are distributed across multiple packing stations with spare capacity. | The system contains a structural bottleneck. | 0 |
train_003 | A clinic has adequate doctors but only one triage nurse processes all arrivals. | The clinic contains a structural bottleneck. | 1 |
train_004 | A clinic distributes triage across multiple staff members. | The clinic contains a structural bottleneck. | 0 |
train_005 | A database cluster has many replicas but all writes pass through one overloaded node. | The database contains a structural bottleneck. | 1 |
train_006 | Database writes are distributed across multiple scalable resources. | The database contains a structural bottleneck. | 0 |
train_007 | A project depends on one specialist to approve every design decision. | The project contains a structural bottleneck. | 1 |
train_008 | Design approval authority is distributed across qualified team members. | The project contains a structural bottleneck. | 0 |
train_009 | A supply chain depends on one port for all international shipments. | The supply chain contains a structural bottleneck. | 1 |
train_010 | The supply chain uses multiple ports and routing options. | The supply chain contains a structural bottleneck. | 0 |
train_011 | A machine line processes materials through one slow inspection station. | The production system contains a structural bottleneck. | 1 |
train_012 | Inspection capacity scales with production volume. | The production system contains a structural bottleneck. | 0 |
train_013 | A support organization routes all escalations through one manager. | The support system contains a structural bottleneck. | 1 |
train_014 | Escalations are distributed across several managers. | The support system contains a structural bottleneck. | 0 |
train_015 | A bridge network relies on one crossing point for all traffic. | The transport system contains a structural bottleneck. | 1 |
train_016 | Traffic can flow through multiple independent crossings. | The transport system contains a structural bottleneck. | 0 |
train_017 | All financial approvals require one executive signature. | The organization contains a structural bottleneck. | 1 |
train_018 | Financial approvals can be completed through multiple authorized pathways. | The organization contains a structural bottleneck. | 0 |
train_019 | A model-serving platform routes all requests through one inference gateway. | The platform contains a structural bottleneck. | 1 |
train_020 | Model requests are balanced across multiple gateways. | The platform contains a structural bottleneck. | 0 |
What this dataset does
This dataset tests whether a model can detect structural bottlenecks.
The task is simple:
Given a scenario and a structural-bottleneck claim, predict whether the claim is supported.
Core stability idea
A structural bottleneck is a constraint that limits system performance regardless of improvements elsewhere.
Typical bottlenecks include:
- single approval points
- single processing nodes
- unique dependencies
- centralized routing
- irreplaceable personnel
- constrained resources
Removing a bottleneck often increases system capacity more effectively than optimizing surrounding components.
Prediction target
Binary label:
- 1 = a structural bottleneck is present
- 0 = a structural bottleneck is not present
Row structure
Each row contains:
- scenario_id
- scenario_text
- claim
- label
Files
- data/train.csv
- data/test.csv
- scorer.py
- README.md
Evaluation
python scorer.py --predictions predictions.csv --truth data/test.csv
Structural Note
This dataset is intentionally small.
Its purpose is to test whether a model can identify limiting constraints embedded in system structure rather than transient operational issues.
License
MIT
- Downloads last month
- 31