Triple
T14274600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITVX |
E353883
|
entity |
| Predicate | premiumTierIncludes |
P68729
|
FINISHED |
| Object | BritBox UK content |
—
|
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: BritBox UK content | Statement: [ITVX, premiumTierIncludes, BritBox UK content]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: premiumTierIncludes Context triple: [ITVX, premiumTierIncludes, BritBox UK content]
-
A.
premiumTierBackedBy
Indicates that a premium tier is supported, guaranteed, or underwritten by a specified backing entity or resource.
-
B.
requiresPremiumFor
Indicates that access to or use of something is conditional on having a premium status, subscription, or account.
-
C.
exclusiveBenefit
Indicates that a benefit is provided to one party or group in a way that excludes others from receiving the same advantage.
-
D.
upgradeIncludes
chosen
Indicates that an upgrade action or package contains, encompasses, or bundles the specified component, feature, or item as part of the upgrade.
-
E.
offersFeature
Indicates that one entity provides or makes available a particular feature or capability to 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6582f5308190969f4cfd724d9139 |
completed | April 14, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69de2a88446481909cd526da97a3b70f |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:10 a.m.