Triple
T31034840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southall rail crash |
E790825
|
entity |
| Predicate | freightTrainType |
P1305
|
FINISHED |
| Object | aggregate train |
—
|
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: aggregate train | Statement: [Southall rail crash, freightTrainType, aggregate train]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: freightTrainType Context triple: [Southall rail crash, freightTrainType, aggregate train]
-
A.
trainTypeUsed
Indicates that a specific type or category of train is employed or operated in a given context or service.
-
B.
freightType
Indicates the category or mode of freight associated with a shipment or transport activity.
-
C.
rollingStockType
chosen
Indicates the specific category or type of railway rolling stock associated with an entity (e.g., locomotive, passenger car, freight wagon).
-
D.
railCarries
Indicates that a rail or railway system transports or conveys a specified entity from one place to another.
-
E.
railroadClass
Indicates the classification or category of a railroad according to an established system (e.g., by size, revenue, or regulatory status).
- 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_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:59 p.m.