Triple
T1343551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lokomotiv Yaroslavl |
E28518
|
entity |
| Predicate | tragedy |
P21136
|
FINISHED |
| Object | 2011 plane crash of team flight near Yaroslavl |
—
|
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: 2011 plane crash of team flight near Yaroslavl | Statement: [Lokomotiv Yaroslavl, tragedy, 2011 plane crash of team flight near Yaroslavl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tragedy Context triple: [Lokomotiv Yaroslavl, tragedy, 2011 plane crash of team flight near Yaroslavl]
-
A.
hasTragicEnding
chosen
Indicates that the event, story, or situation concludes with a sorrowful, disastrous, or otherwise deeply unfortunate outcome.
-
B.
death
Indicates the event or state in which an entity ceases to live or exist, marking the end of its biological or functional processes.
-
C.
sacrifice
Indicates giving up something of value, often for the benefit, protection, or advantage of another entity or goal.
-
D.
dramaticForm
Indicates that one entity is expressed, structured, or realized in the form of a particular dramatic genre or theatrical mode.
-
E.
fate
Indicates that an entity is destined or predetermined to experience a particular outcome or course of events beyond its control.
- 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_69a49854eb3481908c7d56b2e449a290 |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c23b8a9081908b78405d4ef806af |
completed | March 1, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69a4bef3e8fc8190ac9a1ba9b5879483 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.