Triple
T20366072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonos Amp |
E496911
|
entity |
| Predicate | supportsHomeTheaterUse |
P15794
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Sonos Amp, supportsHomeTheaterUse, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsHomeTheaterUse Context triple: [Sonos Amp, supportsHomeTheaterUse, yes]
-
A.
supportsRemotePlay
Indicates that one entity enables or is compatible with remote play functionality for another entity.
-
B.
supportsUse
chosen
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
-
C.
theaterSupport
Indicates that one entity provides assistance, resources, or services to support another entity in the context of theater or theatrical activities.
-
D.
supportsDisplayTechnology
Indicates that one entity is compatible with, or capable of operating using, a specified display technology.
-
E.
supportsDisplayStandard
Indicates that one entity is compatible with and can correctly handle or render the specified display standard.
- 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_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. |
Created at: April 16, 2026, 11:26 a.m.