Triple
T19452238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonos Voice Control |
E486640
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | voice assistant |
C4098
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: voice assistant Context triple: [Sonos Voice Control, instanceOf, voice assistant]
-
A.
intelligent personal assistant
An intelligent personal assistant is a software agent that uses artificial intelligence to understand user requests, manage tasks, and provide personalized information or services through natural language interaction.
-
B.
voice-driven application
A voice-driven application is a software system that allows users to interact and perform tasks primarily through spoken commands and natural language input.
-
C.
voice application platform feature
A voice application platform feature is a functional capability within a voice-enabled system that allows developers or users to create, manage, and enhance interactive voice experiences through tools like speech recognition, natural language understanding, and integration with external services.
-
D.
virtual assistant
chosen
A virtual assistant is an AI-powered software agent that interacts with users through natural language to perform tasks, answer questions, and provide personalized support across digital platforms.
-
E.
speech recognition API
A speech recognition API is a software interface that converts spoken language into machine-readable text or commands, enabling applications to process and respond to voice input.
- F. None of above.
Provenance (1 batch)
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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:38 p.m.