Triple
T14376280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sky Anytime on PC |
E356482
|
entity |
| Predicate | availableContent |
P16209
|
FINISHED |
| Object | live television |
—
|
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: live television | Statement: [Sky Anytime on PC, availableContent, live television]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: availableContent Context triple: [Sky Anytime on PC, availableContent, live television]
-
A.
offersContentType
chosen
Indicates that one entity provides or makes available content of a specified type to another entity or context.
-
B.
contentAccess
Indicates that one entity is permitted to retrieve, view, or otherwise use the content provided or controlled by another entity.
-
C.
contentUsage
Indicates how a piece of content is intended to be used, accessed, or consumed within a given context or system.
-
D.
contentTypesRecommended
Indicates that certain types of content are suggested or recommended in relation to a given entity or context.
-
E.
availableFor
Indicates that one entity can be used, accessed, or allocated for the benefit, purpose, or use of another entity.
- 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de900949fc81909be0da1734c46645 |
completed | April 14, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69de2a9cb3e081909f6b33fdd939bb9e |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:16 a.m.