Triple
T19107106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nevsky Express |
E467683
|
entity |
| Predicate | 2009AccidentLocation |
P26084
|
FINISHED |
| Object | between Moscow and Saint Petersburg |
—
|
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: between Moscow and Saint Petersburg | Statement: [Nevsky Express, 2009AccidentLocation, between Moscow and Saint Petersburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 2009AccidentLocation Context triple: [Nevsky Express, 2009AccidentLocation, between Moscow and Saint Petersburg]
-
A.
siteOfAccident
chosen
Indicates the location where an accident occurred.
-
B.
intendedDestinationAtAccident
Indicates that a location was the destination an entity was heading toward at the time an accident occurred.
-
C.
resultOfAccident
Indicates that something exists or occurs as a consequence or outcome of an accident.
-
D.
accident
Indicates an unintended, unforeseen event or mishap occurring, often resulting in damage, injury, or disruption.
-
E.
hasAccidentAt
Indicates that an accident involving a subject occurs at a specific location or time.
- 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_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. |
Created at: April 10, 2026, 12:04 p.m.