Triple
T19107108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nevsky Express |
E467683
|
entity |
| Predicate | 2009AccidentFatalities |
P134408
|
FINISHED |
| Object | over 20 people |
—
|
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: over 20 people | Statement: [Nevsky Express, 2009AccidentFatalities, over 20 people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 2009AccidentFatalities Context triple: [Nevsky Express, 2009AccidentFatalities, over 20 people]
-
A.
2011AccidentFatalities
Indicates the number of people who died in accidents that occurred in the year 2011.
-
B.
numberOfFatalAccidents
Indicates the total count of accidents within a given context that resulted in at least one fatality.
-
C.
constructionAccidentFatalities
Indicates that a construction-related accident resulted in one or more fatalities.
-
D.
fatalAccident
Indicates that an accident resulted in at least one death.
-
E.
resultOfAccident
Indicates that something exists or occurs as a consequence or outcome of an accident.
- 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e391245c8190b1393577b61c4f76 |
completed | April 20, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e4b9ac41848190afd0f33b42cebe99 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:04 p.m.