Triple
T20030305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shipton-on-Cherwell train crash |
E495103
|
entity |
| Predicate | speedAtDerailment |
P87957
|
FINISHED |
| Object | approximately 40 mph |
—
|
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: approximately 40 mph | Statement: [Shipton-on-Cherwell train crash, speedAtDerailment, approximately 40 mph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speedAtDerailment Context triple: [Shipton-on-Cherwell train crash, speedAtDerailment, approximately 40 mph]
-
A.
speedAtDerailmentApprox
chosen
Indicates the approximate speed an entity was traveling at the moment it derailed.
-
B.
designedSpeedKmH
Indicates the maximum speed in kilometers per hour that something is intended or engineered to achieve under its design specifications.
-
C.
speedClassOfTrains
Indicates the classification of trains based on their operating speed or speed category.
-
D.
numberOfCarsDerailed
Indicates the count of cars that have come off the tracks in a derailment incident.
-
E.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66291a00c8190b0b895909f32d623 |
completed | April 20, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:36 p.m.