Triple
T31034839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southall rail crash |
E790825
|
entity |
| Predicate | freightTrainOperator |
P20222
|
FINISHED |
| Object | EWS |
—
|
NE NERFINISHED |
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: EWS | Statement: [Southall rail crash, freightTrainOperator, EWS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: freightTrainOperator Context triple: [Southall rail crash, freightTrainOperator, EWS]
-
A.
trainOperator
chosen
Indicates that one entity operates, manages, or runs train services for another entity or within a specific rail system.
-
B.
formerRailOperator
Indicates that an entity previously operated a rail service or railway system but no longer does so.
-
C.
hasRailTransportOperator
Indicates that a rail transport system, service, or infrastructure is operated or managed by a specified rail transport operator.
-
D.
freightOperatorOnCorridor
Indicates that a particular freight operator provides services or operates along a specified transport corridor.
-
E.
operatedFreightServiceIn
Indicates that an entity operated a freight transportation service within or across the specified geographic area or route.
- 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_69f224c97a788190b5da1ead6038a74e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f694f4f6e881908e00ff63a092f717 |
completed | May 3, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 8:59 p.m.