Triple
T34884739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | чемпионат мира по хоккею с шайбой 2008 |
E1006111
|
entity |
| Predicate | повод проведения в Канаде |
P181831
|
FINISHED |
| Object | 100-летие канадского хоккея |
—
|
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: 100-летие канадского хоккея | Statement: [чемпионат мира по хоккею с шайбой 2008, повод проведения в Канаде, 100-летие канадского хоккея]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: повод проведения в Канаде Context triple: [чемпионат мира по хоккею с шайбой 2008, повод проведения в Канаде, 100-летие канадского хоккея]
-
A.
outcomeForCanada
Indicates the result, consequence, or impact that something has specifically for Canada.
-
B.
exCanadianNational
Indicates that a person previously held Canadian nationality but no longer does.
-
C.
roadOnCanadianSide
Indicates that the road is located on the Canadian side of a border or boundary.
-
D.
regionCanada
Indicates that an entity is located in, associated with, or pertains to the geographic region of Canada.
-
E.
regionCanadianSide
Indicates that the specified region is located on the Canadian side of a border or boundary.
- 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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782cf61948190b98185d961609554 |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f782c848fc8190baea8c845ca9079f |
completed | May 3, 2026, 5:15 p.m. |
Created at: May 3, 2026, 4 p.m.