Triple
T25889208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFL Sunday Ticket |
E652280
|
entity |
| Predicate | currentDistributor |
P1951
|
FINISHED |
| Object | YouTube TV |
—
|
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: YouTube TV | Statement: [NFL Sunday Ticket, currentDistributor, YouTube TV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentDistributor Context triple: [NFL Sunday Ticket, currentDistributor, YouTube TV]
-
A.
currentDistribution
Indicates the way something is presently allocated, spread, or shared among a set of entities or locations.
-
B.
distributorType
Indicates the specific category or role of a distributor in relation to the distribution of a product or service.
-
C.
distributor
chosen
Indicates that an entity is responsible for supplying, delivering, or making another entity’s products or materials available to others.
-
D.
distributionName
Indicates the name or title assigned to a particular distribution or release of something.
-
E.
distributorContext
Indicates the contextual relationship in which a distributor operates or is relevant to a particular entity, transaction, or scenario.
- 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_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 22, 2026, 8:18 a.m.