Triple
T28453363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Once railway station |
E716638
|
entity |
| Predicate | 2012CrashInjuries |
P165160
|
FINISHED |
| Object | 700+ |
—
|
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: 700+ | Statement: [Once railway station, 2012CrashInjuries, 700+]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 2012CrashInjuries Context triple: [Once railway station, 2012CrashInjuries, 700+]
-
A.
injuredIn
Indicates that an entity sustained an injury as a result of a specified event, situation, or action.
-
B.
involvedInAccident
Indicates that an entity participated in, was affected by, or was otherwise a party to a specific accident or collision event.
-
C.
resultOfAccident
Indicates that something exists or occurs as a consequence or outcome of an accident.
-
D.
accidentOccurredDuring
Indicates that an accident took place within the time span or context of a specified event, activity, or condition.
-
E.
causeOfInjury
Indicates that one entity is the source or reason that another entity sustained an injury.
- 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_69efd6b76f8c8190a7ba908aca280942 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 28, 2026, 1:53 a.m.