Triple
T2855471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Rangers–New York Islanders rivalry |
E63189
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | National Hockey League rivalry |
C11787
|
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: National Hockey League rivalry Context triple: [New York Rangers–New York Islanders rivalry, instanceOf, National Hockey League rivalry]
-
A.
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.
-
B.
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.
-
C.
National Hockey League event
A National Hockey League event is any scheduled or unscheduled occurrence officially organized, sanctioned, or recognized by the NHL, such as games, drafts, ceremonies, or media activities, involving league teams, players, officials, or stakeholders.
-
D.
NHL conference
An NHL conference is one of the league’s two primary groupings of teams, organized mainly by geography, that determines regular-season scheduling and playoff qualification structure.
-
E.
NHL team
An NHL team is a professional ice hockey organization that competes in the National Hockey League, consisting of players, coaches, and staff representing a specific city or region.
- 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_69ab4c407c408190857d25e027155ce9 |
completed | March 6, 2026, 9:50 p.m. |
Created at: March 6, 2026, 10:02 p.m.