Triple
T9302166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hatfield rail crash |
E223790
|
entity |
| Predicate | railwayAccidentCategory |
P1788
|
FINISHED |
| Object | derailment due to track failure |
—
|
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: derailment due to track failure | Statement: [Hatfield rail crash, railwayAccidentCategory, derailment due to track failure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayAccidentCategory Context triple: [Hatfield rail crash, railwayAccidentCategory, derailment due to track failure]
-
A.
accidentType
chosen
Indicates the specific category or kind of accident associated with an event or incident.
-
B.
trainsCategory
Indicates that one entity is a category or type under which the other entity is trained or classified.
-
C.
accident
Indicates an unintended, unforeseen event or mishap occurring, often resulting in damage, injury, or disruption.
-
D.
resultOfAccident
Indicates that something exists or occurs as a consequence or outcome of an accident.
-
E.
siteOfAccident
Indicates the location where an accident occurred.
- 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_69ca8424d0f08190831e2e93c6533aeb |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd08d34c4c819095a213360747c3a6 |
completed | April 1, 2026, noon |
| PD | Predicate disambiguation | batch_69cc7a5ef1908190bc5ca166bb895af6 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:36 p.m.