Triple
T25889202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFL Sunday Ticket |
E652280
|
entity |
| Predicate | formerExclusiveDistributor |
P1951
|
FINISHED |
| Object | DirecTV |
—
|
NE NERFINISHED |
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: DirecTV | Statement: [NFL Sunday Ticket, formerExclusiveDistributor, DirecTV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerExclusiveDistributor Context triple: [NFL Sunday Ticket, formerExclusiveDistributor, DirecTV]
-
A.
brandExclusive
Indicates that something is restricted to, offered only by, or uniquely associated with a single brand.
-
B.
carrierExclusiveVariant
Indicates that a variant is available only through a specific carrier and not through others.
-
C.
franchiseDistributor
Indicates that one entity is authorized to distribute or sell the products or services of another entity under a franchise agreement.
-
D.
distributor
chosen
Indicates that an entity is responsible for supplying, delivering, or making another entity’s products or materials available to others.
-
E.
hasExclusiveContractFor
Indicates that one party holds sole contractual rights to provide, use, or represent a specific product, service, or opportunity, excluding all other potential counterparties.
- 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_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 22, 2026, 8:18 a.m.