Triple
T30440374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soham rail disaster |
E774423
|
entity |
| Predicate | locomotiveName |
P169434
|
FINISHED |
| Object | Doncaster Rovers |
—
|
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: Doncaster Rovers | Statement: [Soham rail disaster, locomotiveName, Doncaster Rovers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locomotiveName Context triple: [Soham rail disaster, locomotiveName, Doncaster Rovers]
-
A.
locomotiveNumber
Indicates the identifying number assigned to a locomotive in the relationship.
-
B.
firstLocomotiveName
Indicates the name assigned to the first locomotive associated with a given entity or context.
-
C.
laterLocomotiveType
Indicates that one locomotive type succeeds or comes after another in time, representing a later development or version in locomotive design.
-
D.
locomotiveSeries
Indicates that one locomotive belongs to, or is classified under, a particular locomotive series or model line.
-
E.
winningLocomotive
Indicates that a locomotive is the one that wins a competition, race, or contest among locomotives.
- 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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6869840948190bdb374de6c9edf96 |
completed | May 2, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 8:08 p.m.