Triple
T24676887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IIHF Competition and Coordination Committee |
E611011
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ice hockey governance committee |
C49499
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: ice hockey governance committee Context triple: [IIHF Competition and Coordination Committee, instanceOf, ice hockey governance committee]
-
A.
IIHF governing body meeting
An IIHF governing body meeting is a formal assembly of International Ice Hockey Federation officials and member representatives convened to discuss, decide, and regulate policies, rules, and strategic directions for international ice hockey.
-
B.
ice hockey department
An ice hockey department is an organizational unit within a club, school, or institution responsible for managing all aspects of its ice hockey activities, including teams, coaching, scheduling, equipment, and competition logistics.
-
C.
ice hockey official
An ice hockey official is a trained individual responsible for enforcing the rules, ensuring fair play, and maintaining game flow and safety during an ice hockey match.
-
D.
national ice hockey federation
A national ice hockey federation is the governing body responsible for organizing, regulating, and promoting ice hockey within a specific country, including overseeing national teams, leagues, and development programs.
-
E.
continental hockey federation
A continental hockey federation is a governing body that oversees, organizes, and regulates ice hockey activities, competitions, and development programs across multiple countries within a specific continent.
- F. None of above. chosen
Provenance (1 batch)
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_69e2c4d5c2dc8190ac857dea25ec6ce9 |
completed | April 17, 2026, 11:40 p.m. |
Created at: April 18, 2026, 3:06 a.m.