Triple
T24508277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivy League (ECAC Hockey) |
E606138
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collegiate ice hockey grouping |
C6943
|
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: collegiate ice hockey grouping Context triple: [Ivy League (ECAC Hockey), instanceOf, collegiate ice hockey grouping]
-
A.
NCAA Division I men's ice hockey team
An NCAA Division I men's ice hockey team is a collegiate squad that competes at the highest level of U.S. university ice hockey under NCAA regulations, representing its institution in conference and national competition.
-
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.
NCAA Division I ice hockey team
An NCAA Division I ice hockey team is a collegiate squad that competes at the highest level of U.S. college ice hockey under NCAA regulations, typically representing a university or college in intercollegiate competition.
-
D.
ice hockey conference
chosen
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.
-
E.
NCAA Division III ice hockey conference
An NCAA Division III ice hockey conference is an organized group of colleges and universities that compete against each other in men's and/or women's ice hockey at the Division III level under shared rules, schedules, and championship structures.
- 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_69e2c4c725148190a4e41577c5cb409c |
completed | April 17, 2026, 11:39 p.m. |
Created at: April 18, 2026, 2:23 a.m.