Triple
T36254843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minnesota youth hockey associations |
E891904
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ice hockey development system |
C16177
|
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 development system Context triple: [Minnesota youth hockey associations, instanceOf, ice hockey development system]
-
A.
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.
-
B.
ice hockey division
An ice hockey division is an organizational grouping of teams within a league, typically based on geography or competitive level, used to structure schedules, standings, and playoff qualification.
-
C.
senior ice hockey league system
A senior ice hockey league system is an organized structure of competitive ice hockey leagues for adult players, typically arranged in tiers or divisions with defined rules, schedules, and pathways for promotion, relegation, and championships.
-
D.
junior ice hockey league
chosen
A junior ice hockey league is an organized competition structure for young players, typically aged 16–20, that develops their skills and showcases talent for higher levels of play.
-
E.
junior ice hockey team
A junior ice hockey team is an organized group of young athletes, typically aged 16–20, who compete in structured ice hockey leagues focused on player development and competitive play.
- 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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.