Triple
T1130404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Football League expansion and realignment |
E23017
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | American football history topic |
C1928
|
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 history topic Context triple: [National Football League expansion and realignment, instanceOf, American football history topic]
-
A.
National Football League history event
chosen
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.
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.
American football culture term
A term from American football culture that encapsulates the sport’s strategies, traditions, jargon, and social rituals shared by players, fans, and media.
-
D.
American football player
An American football player is an athlete who participates in the sport of American football, executing specialized offensive, defensive, or special teams roles within an organized team structure.
-
E.
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.
- 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_69a493ec75988190b63a11bafaec29b4 |
completed | March 1, 2026, 7:30 p.m. |
Created at: March 1, 2026, 7:44 p.m.