Triple
T13807975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NHL expansion of 1967 |
E331808
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sports league expansion |
C7601
|
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: sports league expansion Context triple: [NHL expansion of 1967, instanceOf, sports league expansion]
-
A.
sports league merger
A sports league merger is the unification of two or more separate sports leagues into a single organizational entity, combining their teams, governance structures, and competitive frameworks.
-
B.
professional sports league
A professional sports league is an organized association of teams or athletes that schedules and governs competitive events at the highest level of play, typically offering salaries, standardized rules, and commercialized entertainment.
-
C.
sports league structural history
chosen
The sports league structural history class represents the chronological evolution of a league’s organizational format, including changes in divisions, conferences, team membership, scheduling, and competition rules over time.
-
D.
sports division
A sports division is an organizational unit within a sports league or association that groups teams based on factors like geography, skill level, or age to structure competition and scheduling.
-
E.
professional sports union
A professional sports union is an organized association of athletes in a professional league that collectively represents their interests in negotiations over wages, working conditions, benefits, and other employment-related matters with team owners and league management.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:12 p.m.