Triple
T9339777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFL tiebreaking procedures |
E224734
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | National Football League rule |
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: National Football League rule Context triple: [NFL tiebreaking procedures, instanceOf, National Football League rule]
-
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.
gridiron football league
A gridiron football league is an organized association that schedules, regulates, and oversees competitive American or Canadian football games among member teams within a defined structure and season.
-
C.
foundational document of the National Football League
The foundational document of the National Football League is the core legal and organizational charter that establishes the league’s structure, governance, membership, and fundamental operating principles.
-
D.
National Hockey League rule
A National Hockey League rule is an official, codified regulation that governs gameplay, player conduct, equipment, and officiating procedures in NHL ice hockey competitions.
-
E.
American football official
An American football official is a trained and certified individual responsible for enforcing the rules, ensuring fair play, and managing the flow of an American football game on the field.
- 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_69ca84286fcc81909f6e7fd7a7e862a2 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:40 p.m.