Triple
T29726178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NHL Competition Committee |
E752184
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | National Hockey League body |
C20843
|
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 Hockey League body Context triple: [NHL Competition Committee, instanceOf, National Hockey League body]
-
A.
NHL administrative body
chosen
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.
-
B.
National Hockey League conference
A National Hockey League conference is a major organizational division of NHL teams, grouped primarily by geography, that determines regular-season scheduling and playoff qualification structure.
-
C.
National Hockey League division
A National Hockey League division is a grouping of NHL teams, typically organized by geography, used to structure the regular-season schedule and determine playoff qualification and seeding.
-
D.
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.
-
E.
National Hockey League event
A National Hockey League event is any scheduled or unscheduled occurrence officially organized, sanctioned, or recognized by the NHL, such as games, drafts, ceremonies, or media activities, involving league teams, players, officials, or stakeholders.
- 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 7:39 p.m.