Triple
T34884699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | чемпионат мира по хоккею с шайбой 2008 |
E1006111
|
entity |
| Predicate | организатор |
P56473
|
FINISHED |
| Object | IIHF |
—
|
NE NERFINISHED |
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: IIHF | Statement: [чемпионат мира по хоккею с шайбой 2008, организатор, IIHF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: организатор Context triple: [чемпионат мира по хоккею с шайбой 2008, организатор, IIHF]
-
A.
principalOrganizer
Indicates that an entity serves as the main or leading organizer responsible for planning or coordinating another entity or event.
-
B.
organizerRole
Indicates that an entity has the role or responsibility of organizing an event, activity, or group.
-
C.
firstOrganizer
Indicates that an entity serves as the primary or initial organizer in relation to another event, group, or activity.
-
D.
organizers
chosen
Indicates that one or more entities are responsible for planning, coordinating, or managing an event, activity, or group.
-
E.
co-organizerOf
Indicates that an entity shares responsibility with others in planning, coordinating, or managing an event, project, or activity.
- 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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.