Triple
T17711478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freeview (New Zealand) |
E441575
|
entity |
| Predicate | supportsReceptionDevice |
P126386
|
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: [Freeview (New Zealand), supportsReceptionDevice, set-top box]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsReceptionDevice Context triple: [Freeview (New Zealand), supportsReceptionDevice, set-top box]
-
A.
supportsDeviceCategory
Indicates that one entity is compatible with and can operate or accommodate a specified category of devices.
-
B.
supportedEquipment
chosen
Indicates that one entity provides compatibility with, or operational support for, a specified piece of equipment.
-
C.
requiresDevice
Indicates that performing the specified action or relationship is contingent on the presence or use of a particular device.
-
D.
usesDevice
Indicates that one entity operates, employs, or relies on a particular device to perform an action or achieve a purpose.
-
E.
supportedAs
Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4729b5d3c819085613ed25dc6761d |
completed | April 19, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:05 a.m.