Triple
T1290404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Positive Train Control |
E27532
|
entity |
| Predicate | monitoredHazard |
P9979
|
FINISHED |
| Object | overspeed conditions |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: overspeed conditions | Statement: [Positive Train Control, monitoredHazard, overspeed conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monitoredHazard Context triple: [Positive Train Control, monitoredHazard, overspeed conditions]
-
A.
hasNotableHazard
Indicates that an entity is associated with a significant risk, danger, or harmful condition that is noteworthy or exceptional.
-
B.
hazardType
Indicates the specific kind or category of hazard associated with an entity or situation.
-
C.
hazardScope
Indicates the range or extent within which a particular hazard is relevant, applicable, or has effect.
-
D.
monitoredFor
chosen
Indicates that one entity is being observed or tracked over time to detect, assess, or manage the occurrence or progression of another entity (such as a condition, event, or risk).
-
E.
hasClimbingHazard
Indicates that something presents a risk or danger specifically associated with climbing activities.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0d6af908190ade9c481cc6f0ad8 |
completed | March 1, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69a4bee41ca08190b0ad6f7ea40c0b62 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.