Triple
T14792075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thanksgiving games |
E347680
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | National Football League tradition |
C33960
|
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 Football League tradition Context triple: [Thanksgiving games, instanceOf, National Football League tradition]
-
A.
National Football League history event
A National Football League history event is a significant occurrence or milestone—such as a game, rule change, record, or organizational decision—that has contributed to shaping the evolution and legacy of the NFL over time.
-
B.
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.
-
C.
college football tradition
A college football tradition is a recurring, culturally significant practice or ritual associated with a team, game day, or fan base that reinforces school identity, community, and continuity over time.
-
D.
National Football League topic
chosen
A National Football League topic represents any subject, discussion, or piece of information specifically related to the teams, players, games, rules, history, or operations of the NFL.
-
E.
American football dynasty
An American football dynasty is a team that achieves sustained, dominant success over multiple seasons or eras, typically marked by repeated championships and consistent elite performance.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:31 a.m.