Triple
T24469599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PairWise Rankings |
E617062
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | college ice hockey ranking |
C49039
|
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: college ice hockey ranking Context triple: [PairWise Rankings, instanceOf, college ice hockey ranking]
-
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.
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.
-
C.
continental hockey federation
A continental hockey federation is a governing body that oversees, organizes, and regulates ice hockey activities, competitions, and development programs across multiple countries within a specific continent.
-
D.
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.
-
E.
ice hockey rivalry
An ice hockey rivalry is a competitive and often intense ongoing relationship between two ice hockey teams, fueled by repeated matchups, historical context, geographic proximity, or cultural factors that heighten fan and player emotions.
- 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:20 a.m.