Triple
T20642677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Original Six |
E507270
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | group of National Hockey League teams |
C1268
|
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: group of National Hockey League teams Context triple: [Original Six, instanceOf, group of National Hockey League teams]
-
A.
NHL team
An NHL team is a professional ice hockey organization that competes in the National Hockey League, consisting of players, coaches, and staff representing a specific city or region.
-
B.
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.
-
C.
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.
-
D.
National Hockey League conference
chosen
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.
-
E.
National Hockey Association team
A National Hockey Association team is a professional ice hockey club that competed in the early 20th-century NHA league, representing a specific city or region and comprising players, coaches, and management organized to participate in scheduled league competition.
- 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_69e0b4be702c8190a3d2410a881d310a |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:43 a.m.