Triple
T20366077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonos Amp |
E496911
|
entity |
| Predicate | supportsSubwoofer |
P139863
|
FINISHED |
| Object | powered subwoofer via RCA |
—
|
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: powered subwoofer via RCA | Statement: [Sonos Amp, supportsSubwoofer, powered subwoofer via RCA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSubwoofer Context triple: [Sonos Amp, supportsSubwoofer, powered subwoofer via RCA]
-
A.
hasLFEChannels
Indicates that an entity includes or is associated with one or more Low-Frequency Effects (LFE) audio channels.
-
B.
supportsSubbands
Indicates that one entity provides or is compatible with multiple subbands within a broader frequency or spectral band.
-
C.
supportsDownmixing
Indicates that one entity can convert or mix multi-channel audio into a format with fewer channels (e.g., surround sound to stereo).
-
D.
hasAcousticsSuitableFor
Indicates that something possesses acoustic properties that are appropriate or well-suited for a particular use, activity, or environment.
-
E.
supportsVolumeControl
Indicates that one entity provides the capability to adjust or manage the audio volume level of another entity.
- F. None of above. chosen
Provenance (4 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_69e0b4a4f9b081908a5a021919c21ccb |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67871bfdc8190948c46497cd675c9 |
completed | April 20, 2026, 7:03 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:26 a.m.