Triple
T25889214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFL Sunday Ticket |
E652280
|
entity |
| Predicate | rightsDealStartSeason |
P3615
|
FINISHED |
| Object | 2023 NFL season |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 2023 NFL season | Statement: [NFL Sunday Ticket, rightsDealStartSeason, 2023 NFL season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rightsDealStartSeason Context triple: [NFL Sunday Ticket, rightsDealStartSeason, 2023 NFL season]
-
A.
contractStartSeason
chosen
Indicates the season during which a contract between entities begins or becomes effective.
-
B.
rightsAgreementStart
Indicates the date or point in time when a rights-related agreement or contract becomes effective.
-
C.
networkRightsDeal
Indicates a contractual agreement granting a network the rights to distribute, broadcast, or otherwise exploit specified content.
-
D.
televisionRightsDealYear
Indicates the year in which a deal granting rights to televise something (such as an event, program, or content) was made or took effect.
-
E.
tradeSeason
Indicates a specific period or season during which trading activities or exchanges are allowed, active, or most commonly occur.
- F. None of above.
Provenance (3 batches)
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_69e7ab3b92cc81908febd90317862647 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f603452e3c8190a027cd2a9910c344 |
completed | May 2, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 8:18 a.m.