Triple
T14375876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sky’s triple‑play services |
E356471
|
entity |
| Predicate | mayIncludeEquipment |
P2728
|
FINISHED |
| Object | set‑top box |
—
|
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: set‑top box | Statement: [Sky’s triple‑play services, mayIncludeEquipment, set‑top box]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayIncludeEquipment Context triple: [Sky’s triple‑play services, mayIncludeEquipment, set‑top box]
-
A.
mayIncludeFeature
Indicates that one entity is allowed or able to contain, incorporate, or be associated with a particular feature.
-
B.
usesEquipment
chosen
Indicates that an entity employs or operates a particular piece of equipment to perform an action or fulfill a function.
-
C.
mayBeWorn
Indicates that one entity is suitable or allowed to be worn by another entity, typically as clothing, accessories, or adornment.
-
D.
mayNotFit
Indicates that one entity is unlikely or not expected to be suitable in size, capacity, or compatibility to be placed into, combined with, or used within another entity or context.
-
E.
mayIncludeUnitType
Indicates that something is allowed to contain or be associated with a particular type of unit.
- 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.