Triple
T36885770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colwich Junction |
E911604
|
entity |
| Predicate | railCrashType |
P1788
|
FINISHED |
| Object | head-on collision |
—
|
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: head-on collision | Statement: [Colwich Junction, railCrashType, head-on collision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railCrashType Context triple: [Colwich Junction, railCrashType, head-on collision]
-
A.
accidentType
chosen
Indicates the specific category or kind of accident associated with an event or incident.
-
B.
railDisasterCargo
Indicates a rail transport accident or disaster specifically involving cargo or freight.
-
C.
railDisasterLedTo
Indicates that a specific rail disaster resulted in, caused, or gave rise to a particular subsequent event, consequence, or outcome.
-
D.
railDisasterCasualties
Indicates the number of people killed or injured as a result of a specific rail disaster.
-
E.
resultOfAccident
Indicates that something exists or occurs as a consequence or outcome of an accident.
- 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_69f76e8335908190b77e7e11d0e80820 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.