Triple
T5980773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston University–Boston College men's ice hockey rivalry |
E133113
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | college ice hockey rivalry |
C2754
|
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 rivalry Context triple: [Boston University–Boston College men's ice hockey rivalry, instanceOf, college ice hockey rivalry]
-
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.
National Hockey League rivalry
A National Hockey League rivalry is a recurring, emotionally charged competitive relationship between two NHL teams, fueled by historical context, frequent matchups, geographic proximity, or playoff encounters, that intensifies fan engagement and on-ice competition.
-
C.
ice hockey competition
chosen
An ice hockey competition is an organized event in which teams play regulated ice hockey games against each other to determine rankings, winners, or championships.
-
D.
college baseball rivalry game
A college baseball rivalry game is a highly anticipated, emotionally charged matchup between two collegiate teams with a long-standing competitive history, often drawing large crowds and heightened media attention.
-
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.
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_69c0086f45e8819098f73dd16d45ec9d |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:04 p.m.