Triple
T31034821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southall rail crash |
E790825
|
entity |
| Predicate | speedOfHighSpeedTrain |
P171121
|
FINISHED |
| Object | about 125 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: about 125 mph | Statement: [Southall rail crash, speedOfHighSpeedTrain, about 125 mph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speedOfHighSpeedTrain Context triple: [Southall rail crash, speedOfHighSpeedTrain, about 125 mph]
-
A.
speedClassOfTrains
Indicates the classification of trains based on their operating speed or speed category.
-
B.
relativeSpeedComparedToConventionalTrains
Indicates how the speed of something compares to that of conventional trains, typically expressing whether it is faster, slower, or similar.
-
C.
hasHighSpeedLine
Indicates that there exists a high-speed rail line connection between the related entities.
-
D.
hasHighSpeedSections
Indicates that the entity includes segments or portions where operation or movement occurs at high speed.
-
E.
firstHighSpeedRailIn
Indicates that a given rail system is the earliest high-speed rail established within a specified region or country.
- F. None of above. chosen
Provenance (4 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_69f224c97a788190b5da1ead6038a74e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f698ad83a08190a6834056ccc3e3a4 |
completed | May 3, 2026, 12:37 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f697e92e2c8190bed50d5ba0981b64 |
completed | May 3, 2026, 12:33 a.m. |
Created at: April 29, 2026, 8:59 p.m.