Triple
T23771355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CIHA |
E587534
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | national ice hockey governing body |
C14493
|
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: national ice hockey governing body Context triple: [CIHA, instanceOf, national ice hockey governing body]
-
A.
national ice hockey federation
chosen
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.
-
B.
national ice hockey association
A national ice hockey association is the governing body responsible for organizing, regulating, and promoting ice hockey activities and competitions within a specific country.
-
C.
NHL administrative body
The NHL administrative body is the central organizational authority responsible for governing league operations, enforcing rules and policies, managing business affairs, and coordinating activities among teams, players, and stakeholders within the National Hockey League.
-
D.
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.
-
E.
national ice hockey team
A national ice hockey team is an officially recognized representative squad composed of the best eligible players from a country, competing in international ice hockey tournaments and matches under that nation’s flag.
- F. None of above.
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_69e2490d245881909028226a1393d624 |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 7:15 p.m.