scenario_id string | scenario_text string | claim string | label int64 |
|---|---|---|---|
train_001 | A patient is stable after treatment, and additional intervention may cause side effects. The team continues observation. | Stability is preserved through silence or restraint. | 1 |
train_002 | A patient is deteriorating rapidly, and the team waits without monitoring or treatment. | Stability is preserved through silence or restraint. | 0 |
train_003 | A server is recovering after rollback, and engineers avoid further changes while monitoring stabilizes. | Stability is preserved through silence or restraint. | 1 |
train_004 | A server is failing under load, and engineers avoid action despite worsening alerts. | Stability is preserved through silence or restraint. | 0 |
train_005 | A conflict between teams is cooling down, and leadership pauses messaging while facts are gathered. | Stability is preserved through silence or restraint. | 1 |
train_006 | A conflict between teams is escalating, and leadership refuses to clarify roles or risks. | Stability is preserved through silence or restraint. | 0 |
train_007 | A model output is uncertain, and the system withholds an answer rather than fabricating certainty. | Stability is preserved through silence or restraint. | 1 |
train_008 | A model output is harmful, and the system remains silent without routing the case for review. | Stability is preserved through silence or restraint. | 0 |
train_009 | A project is recovering after scope reduction, and managers avoid adding new requirements. | Stability is preserved through silence or restraint. | 1 |
train_010 | A project is collapsing from unresolved blockers, and managers delay all decisions. | Stability is preserved through silence or restraint. | 0 |
train_011 | A market panic is easing, and the organization avoids unnecessary public statements that could restart anxiety. | Stability is preserved through silence or restraint. | 1 |
train_012 | A market panic is worsening due to missing information, and the organization withholds essential facts. | Stability is preserved through silence or restraint. | 0 |
train_013 | A machine has just been repaired, and operators run it below peak load while readings normalize. | Stability is preserved through silence or restraint. | 1 |
train_014 | A machine is overheating, and operators ignore alarms to avoid interrupting production. | Stability is preserved through silence or restraint. | 0 |
train_015 | A support issue is being investigated, and staff avoid promising a fix before cause is known. | Stability is preserved through silence or restraint. | 1 |
train_016 | A support outage affects many users, and staff provide no update despite confirmed impact. | Stability is preserved through silence or restraint. | 0 |
train_017 | A damp repair is drying out, and further internal work is paused until moisture readings settle. | Stability is preserved through silence or restraint. | 1 |
train_018 | Water ingress is active, and repair is delayed with no inspection. | Stability is preserved through silence or restraint. | 0 |
train_019 | A team is overloaded, and leadership protects focus time by refusing nonurgent meetings. | Stability is preserved through silence or restraint. | 1 |
train_020 | A team is overloaded because responsibilities are unclear, and leadership avoids clarification. | Stability is preserved through silence or restraint. | 0 |
README.md exists but content is empty.
- Downloads last month
- 11