Triple
T31034834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southall rail crash |
E790825
|
entity |
| Predicate | followedByInContext |
P194134
|
FINISHED |
| Object | Ladbroke Grove rail crash |
—
|
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: Ladbroke Grove rail crash | Statement: [Southall rail crash, followedByInContext, Ladbroke Grove rail crash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedByInContext Context triple: [Southall rail crash, followedByInContext, Ladbroke Grove rail crash]
-
A.
followedByInSequence
Indicates that one event or element directly succeeds another in an ordered sequence.
-
B.
followedByComponent
Indicates that one component directly succeeds another component in a defined sequence or order.
-
C.
followedByClass
Indicates that one class or type is immediately succeeded by another class or type in a defined sequence or ordering.
-
D.
followedByInProtocol
Indicates that one step, action, or event in a protocol occurs immediately after another as the next prescribed step.
-
E.
followsIn
Indicates that one entity comes after or succeeds another in a sequence, order, or progression.
- 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_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
| PDg | Predicate description generation | batch_69fd64bb345c819096a35c72784a8ce3 |
completed | May 8, 2026, 4:21 a.m. |
Created at: April 29, 2026, 8:59 p.m.