Triple
T25889220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFL Sunday Ticket |
E652280
|
entity |
| Predicate | excludesContentType |
P3119
|
FINISHED |
| Object | most playoff games |
—
|
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: most playoff games | Statement: [NFL Sunday Ticket, excludesContentType, most playoff games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: excludesContentType Context triple: [NFL Sunday Ticket, excludesContentType, most playoff games]
-
A.
excludesFormat
Indicates that one entity explicitly disallows or omits a particular format from the set of acceptable or supported formats in a given context.
-
B.
excludesConstruct
Indicates that one entity explicitly omits, leaves out, or does not incorporate a particular construct in its definition, composition, or scope.
-
C.
excludesMode
Indicates that one mode, option, or operational state is defined as incompatible with and therefore prevents the use of another mode.
-
D.
excludes
chosen
Indicates that one entity deliberately omits, leaves out, or does not allow the inclusion of another entity within a set, group, or context.
-
E.
hasContentType
Indicates that an entity is associated with or classified by a specific type of content.
- 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_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 22, 2026, 8:18 a.m.