Triple
T34574773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto Argonauts–Hamilton Tiger-Cats rivalry |
E887720
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Canadian football rivalry |
C61248
|
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: Canadian football rivalry Context triple: [Toronto Argonauts–Hamilton Tiger-Cats rivalry, instanceOf, Canadian football rivalry]
-
A.
Canadian Football League rivalry
chosen
A Canadian Football League rivalry is a recurring, emotionally charged competition between two CFL teams, rooted in historical matchups, regional identities, and fan traditions that intensify the significance of their games.
-
B.
Canadian football league
The Canadian Football League is a professional sports organization that oversees and operates teams competing in Canadian-style gridiron football across Canada.
-
C.
Canadian Football League tradition
The Canadian Football League tradition encompasses the enduring customs, rivalries, community rituals, and cultural practices that have developed around Canadian professional football, especially its distinctive rules, Grey Cup festivities, and regional fan identities.
-
D.
Canadian Football League event
A Canadian Football League event is an organized occurrence related to the CFL, such as a game, draft, award ceremony, or official league function involving its teams, players, or operations.
-
E.
Canadian football team
A Canadian football team is an organized group of players, coaches, and staff that competes in Canadian football competitions under a shared name, identity, and governance structure.
- 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:03 a.m.