Triple
T30440384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soham rail disaster |
E774423
|
entity |
| Predicate | crewMemberInjured |
P52515
|
FINISHED |
| Object | guard Herbert Clarke |
—
|
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: guard Herbert Clarke | Statement: [Soham rail disaster, crewMemberInjured, guard Herbert Clarke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewMemberInjured Context triple: [Soham rail disaster, crewMemberInjured, guard Herbert Clarke]
-
A.
hasInjuredPerson
chosen
Indicates that an entity has a person who has been harmed or injured associated with it.
-
B.
injuredIn
Indicates that an entity sustained an injury as a result of a specified event, situation, or action.
-
C.
crewFatality
Indicates that one or more members of a crew have died as a result of the related event or situation.
-
D.
hasPlaceOfInjury
Indicates that an injury occurred at a specific place or location.
-
E.
hasInjuries
Indicates that an entity has sustained one or more physical or bodily injuries.
- 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_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_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:08 p.m.