Triple
T27909662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midwest Division (AHL) |
E705888
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former American Hockey League division |
C7808
|
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: former American Hockey League division Context triple: [Midwest Division (AHL), instanceOf, former American Hockey League division]
-
A.
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.
-
B.
ice hockey division
chosen
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.
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.
-
D.
United States Hockey League competition
A United States Hockey League competition is an organized ice hockey contest or series of contests held under the governance and rules of the USHL, typically involving junior-level teams competing for standings, titles, or championships.
-
E.
National Lacrosse League division
A National Lacrosse League division is an organizational grouping of NLL teams, typically based on geography or competitive structure, used to arrange regular-season schedules and determine playoff qualification.
- 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_69ef96b5aad08190be36a277c31e7004 |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 6:48 p.m.