Triple
T6059989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston University–Northeastern men's ice hockey rivalry |
E135009
|
entity |
| Predicate | sharesContextWith |
P68404
|
FINISHED |
| Object | Boston College–Boston University men's ice hockey rivalry |
E133113
|
NE FINISHED |
How this triple was built (3 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Boston College–Boston University men's ice hockey rivalry | Statement: [Boston University–Northeastern men's ice hockey rivalry, sharesContextWith, Boston College–Boston University men's ice hockey rivalry]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Boston College–Boston University men's ice hockey rivalry Context triple: [Boston University–Northeastern men's ice hockey rivalry, sharesContextWith, Boston College–Boston University men's ice hockey rivalry]
-
A.
Boston University–Boston College men's ice hockey rivalry
chosen
The Boston University–Boston College men's ice hockey rivalry is one of the most storied and intense matchups in U.S. college hockey, featuring two powerhouse programs that frequently clash in high-stakes games and tournaments.
-
B.
Boston University–Northeastern men's ice hockey rivalry
The Boston University–Northeastern men's ice hockey rivalry is a historic and intense Boston-based college hockey matchup, particularly prominent through their frequent and high-stakes meetings in the annual Beanpot tournament.
-
C.
Boston University Terriers men's ice hockey
The Boston University Terriers men's ice hockey team is a storied NCAA Division I program known for its multiple national championships, intense Beanpot Tournament presence, and historic rivalries within Boston's college hockey scene.
-
D.
Boston College Eagles men's ice hockey
The Boston College Eagles men's ice hockey team is a storied NCAA Division I program known for its multiple national championships, strong Hockey East presence, and intense rivalries with other Boston-area schools.
-
E.
Yale–Harvard rivalry
The Yale–Harvard rivalry is a historic and intense intercollegiate sports competition between Yale University and Harvard University that spans multiple athletic programs and is one of the most famous rivalries in American college sports.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesContextWith Context triple: [Boston University–Northeastern men's ice hockey rivalry, sharesContextWith, Boston College–Boston University men's ice hockey rivalry]
-
A.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
B.
sharesModuleWith
Indicates that two entities are associated with or participate in at least one common module.
-
C.
sharesBaseWith
Indicates that two entities have a common underlying base element, source, or component from which they are derived or constructed.
-
D.
sharesSystemWith
Indicates that two entities operate within or are associated with the same overarching system or environment.
-
E.
sharesAreaWith
Indicates that two entities occupy or overlap the same geographic or spatial area.
- F. None of above. chosen
Provenance (5 batches)
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_69c00878d06881909ee78e88913bf890 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0571e479c8190bec0e1439b4cf68f |
completed | March 22, 2026, 8:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c11d13627081908a4b1d758ecb8ddc |
completed | March 23, 2026, 10:59 a.m. |
| PD | Predicate disambiguation | batch_69c049f031408190b08b2766237c5dd0 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8d4a148190bd8f95caae978e1b |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:10 p.m.