Triple
T26021265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amazon Smart Home ecosystem |
E647157
|
entity |
| Predicate | supportsControlInterface |
P74469
|
FINISHED |
| Object | voice control |
—
|
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: voice control | Statement: [Amazon Smart Home ecosystem, supportsControlInterface, voice control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsControlInterface Context triple: [Amazon Smart Home ecosystem, supportsControlInterface, voice control]
-
A.
supportsControllerInput
chosen
Indicates that an entity is capable of receiving and handling input from a controller device.
-
B.
hasControlService
Indicates that one entity provides or performs a control-related service for another entity.
-
C.
supportsCommandAndControl
Indicates that an entity enables, facilitates, or maintains command-and-control functions for another entity or operation.
-
D.
supportsImmediateControl
Indicates that one entity enables or allows another entity to exercise direct, real-time control over it without intermediate steps or delays.
-
E.
canBeControlledFrom
Indicates that one entity has the ability or authority to operate, direct, or manage another entity remotely or indirectly.
- 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_69e77e8aa65881909ca58918f29ab2a0 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: April 22, 2026, 9:04 a.m.