Triple
T4681916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junior Hockey League (MHL) |
E103822
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | junior ice hockey league |
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: junior ice hockey league Context triple: [Junior Hockey League (MHL), instanceOf, junior ice hockey league]
-
A.
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.
-
B.
major junior ice hockey league
A major junior ice hockey league is a high-level, youth-focused competitive organization, typically for players aged 16–20, that serves as a primary development pathway to professional ice hockey.
-
C.
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.
-
D.
major junior ice hockey team
A major junior ice hockey team is a high-level, youth-focused competitive hockey club, typically composed of players aged 16–20, that competes in a top-tier junior league and serves as a primary development path toward professional play.
-
E.
ice hockey conference
An ice hockey conference is an organized grouping of teams within a larger league structure that compete primarily against each other during a season to determine standings and playoff qualification.
- F. None of above. chosen
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_69bd43debbf08190b4bc372e286ec234 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:16 p.m.