Triple
T6004231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Carolina Central–North Carolina A&T rivalry |
E133668
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | American football 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: American football rivalry Context triple: [North Carolina Central–North Carolina A&T rivalry, instanceOf, American football 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.
American football game
An American football game is a competitive sporting event in which two teams attempt to advance an oval-shaped ball into the opponent’s end zone through a series of timed plays to score points and determine a winner.
-
C.
AFC North rivalry
AFC North rivalry is the intense, historically rooted competition among the NFL’s AFC North teams—primarily the Baltimore Ravens, Cincinnati Bengals, Cleveland Browns, and Pittsburgh Steelers—marked by physical play, passionate fan bases, and frequent high-stakes matchups.
-
D.
American football conference
An American football conference is an organizational grouping of teams within a league, typically structured to manage competition, scheduling, and playoff qualification among its member clubs.
-
E.
American football television program
An American football television program is a broadcast show that presents live or recorded American football games, along with commentary, analysis, highlights, and related features for viewers.
- 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_69c00872444c8190bfaf1739dcec765c |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:06 p.m.