Triple
T22727860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Boroughs |
E562045
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | NBA rivalry |
C778
|
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: NBA rivalry Context triple: [Battle of the Boroughs, instanceOf, NBA rivalry]
-
A.
sports rivalry
chosen
A sports rivalry is a competitive relationship between teams, athletes, or fan bases characterized by repeated contests, heightened emotions, and historical or cultural significance that intensifies their matchups.
-
B.
college basketball rivalry
A college basketball rivalry is a recurring, highly competitive series of games between two collegiate teams characterized by historical significance, regional or conference proximity, and intense fan and media interest.
-
C.
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.
-
D.
National Basketball Association division
A National Basketball Association division is a grouping of NBA teams, typically organized by geographic region, used to structure the regular-season schedule and standings within the league’s conferences.
-
E.
NBA team
An NBA team is a professional basketball organization that competes in the National Basketball Association, consisting of players, coaches, and staff representing a specific city or region.
- 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_69e24550859c81908727d91efc3a81b4 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:21 p.m.