uid stringclasses 10
values | dataset_id stringclasses 1
value | port stringclasses 10
values | storm_intensity_signal stringclasses 3
values | storm_distance_signal stringclasses 3
values | port_backlog_signal stringclasses 3
values | reroute_capacity_signal stringclasses 3
values | ops_summary stringclasses 10
values | question stringclasses 1
value | ground_truth_label stringclasses 2
values | ground_truth_rationale stringclasses 10
values | outcome_signal stringclasses 6
values | source_citation stringclasses 1
value |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
WPL-001 | weather-port-logistics-coherence-break-risk-v0.1 | Rotterdam | low | far | low | high | Storm distant and port clear. | Is weather vs port flow coherent. Answer coherent or incoherent. | coherent | No immediate disruption. | stable | Synthetic |
WPL-002 | weather-port-logistics-coherence-break-risk-v0.1 | LA-LongBeach | high | near | high | low | Major storm approaching congested port. | Is weather vs port flow coherent. Answer coherent or incoherent. | incoherent | Backlog with low reroute. | closure_risk | Synthetic |
WPL-003 | weather-port-logistics-coherence-break-risk-v0.1 | Singapore | moderate | mid | low | high | Storm mid-distance but strong reroute capacity. | Is weather vs port flow coherent. Answer coherent or incoherent. | coherent | System resilient. | stable | Synthetic |
WPL-004 | weather-port-logistics-coherence-break-risk-v0.1 | Shanghai | high | near | high | low | Typhoon with backlog and weak diversion. | Is weather vs port flow coherent. Answer coherent or incoherent. | incoherent | Disruption imminent. | throughput_collapse | Synthetic |
WPL-005 | weather-port-logistics-coherence-break-risk-v0.1 | Antwerp | low | far | moderate | high | Minor weather and strong flexibility. | Is weather vs port flow coherent. Answer coherent or incoherent. | coherent | Balanced. | stable | Synthetic |
WPL-006 | weather-port-logistics-coherence-break-risk-v0.1 | NY-NJ | moderate | near | high | moderate | Storm near with growing queue. | Is weather vs port flow coherent. Answer coherent or incoherent. | incoherent | Stress building. | delay_spike | Synthetic |
WPL-007 | weather-port-logistics-coherence-break-risk-v0.1 | Busan | low | far | low | high | Clear weather and spare capacity. | Is weather vs port flow coherent. Answer coherent or incoherent. | coherent | No mismatch. | stable | Synthetic |
WPL-008 | weather-port-logistics-coherence-break-risk-v0.1 | Mumbai | high | near | moderate | low | Cyclone risk with limited reroute. | Is weather vs port flow coherent. Answer coherent or incoherent. | incoherent | Throughput risk. | reroute_failure | Synthetic |
WPL-009 | weather-port-logistics-coherence-break-risk-v0.1 | Tokyo | moderate | mid | low | high | Storm but strong mitigation. | Is weather vs port flow coherent. Answer coherent or incoherent. | coherent | Handled. | stable | Synthetic |
WPL-010 | weather-port-logistics-coherence-break-risk-v0.1 | Santos | high | near | high | low | Storm surge and congestion. | Is weather vs port flow coherent. Answer coherent or incoherent. | incoherent | Break risk. | closure | Synthetic |
What this repo is for
Detect when storm trajectory and port throughput
decouple
before container backlogs port closures or reroute cascades.
- Downloads last month
- 18