Triple
T23383436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cowden railway station |
E593811
|
entity |
| Predicate | hasAccident |
P32122
|
FINISHED |
| Object | Cowden rail crash |
—
|
NE NERFINISHED |
How this triple was built (3 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: Cowden rail crash | Statement: [Cowden railway station, hasAccident, Cowden rail crash]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cowden rail crash Context triple: [Cowden railway station, hasAccident, Cowden rail crash]
-
A.
Hatfield rail crash
The Hatfield rail crash was a fatal 2000 train derailment in Hertfordshire, England, that exposed serious track maintenance failures and triggered major reforms in the UK rail industry.
-
B.
Harrow and Wealdstone rail crash
The Harrow and Wealdstone rail crash was a catastrophic 1952 railway accident in London involving multiple trains, resulting in one of the deadliest peacetime rail disasters in British history.
-
C.
Southall rail crash
The Southall rail crash was a major 1997 high-speed train collision in West London that killed seven people, injured dozens, and raised serious concerns about railway safety and signal-passing procedures in the UK.
-
D.
Charfield rail disaster
The Charfield rail disaster was a 1928 railway accident in Gloucestershire, England, in which an express train collided with a freight train and caught fire, killing 16 people and leaving two child victims famously unidentified.
-
E.
Ladbroke Grove rail crash
The Ladbroke Grove rail crash was a major 1999 train collision near Paddington Station in London that resulted in 31 deaths, over 500 injuries, and significant scrutiny of UK rail safety and signaling practices.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Cowden rail crash Target entity description: The Cowden rail crash was a fatal 1994 head-on collision between two passenger trains in Kent, England, caused by a signal passed at danger on a single-track line.
-
A.
Hatfield rail crash
The Hatfield rail crash was a fatal 2000 train derailment in Hertfordshire, England, that exposed serious track maintenance failures and triggered major reforms in the UK rail industry.
-
B.
Harrow and Wealdstone rail crash
The Harrow and Wealdstone rail crash was a catastrophic 1952 railway accident in London involving multiple trains, resulting in one of the deadliest peacetime rail disasters in British history.
-
C.
Southall rail crash
The Southall rail crash was a major 1997 high-speed train collision in West London that killed seven people, injured dozens, and raised serious concerns about railway safety and signal-passing procedures in the UK.
-
D.
Charfield rail disaster
The Charfield rail disaster was a 1928 railway accident in Gloucestershire, England, in which an express train collided with a freight train and caught fire, killing 16 people and leaving two child victims famously unidentified.
-
E.
Ladbroke Grove rail crash
The Ladbroke Grove rail crash was a major 1999 train collision near Paddington Station in London that resulted in 31 deaths, over 500 injuries, and significant scrutiny of UK rail safety and signaling practices.
- F. None of above. chosen
Provenance (2 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_69e25d268a50819095f2fd479da8ef3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a496ae34819090e86c89eef6d2dc |
completed | April 29, 2026, 6:26 a.m. |
Created at: April 17, 2026, 5:34 p.m.