Triple
T4106803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dolby Headphone |
E88471
|
entity |
| Predicate | audioChannelsSupported |
P14387
|
FINISHED |
| Object | 5.1 surround sound |
—
|
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: 5.1 surround sound | Statement: [Dolby Headphone, audioChannelsSupported, 5.1 surround sound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audioChannelsSupported Context triple: [Dolby Headphone, audioChannelsSupported, 5.1 surround sound]
-
A.
audioChannels
chosen
Indicates the number or configuration of distinct audio signal paths (such as mono, stereo, or surround) used in a recording, transmission, or playback.
-
B.
hasNumberOfAmplifierChannels
Indicates the relationship that specifies how many amplifier channels are present or supported in the associated entity.
-
C.
surroundChannelType
Indicates that an audio channel is designated as part of a surround sound configuration (e.g., rear, side, or height channels) rather than a standard stereo or mono channel.
-
D.
supportsAudioReturnChannel
Indicates that one entity is capable of handling an audio return channel from another entity, allowing audio to be sent back over the same connection.
-
E.
supportsChannels
Indicates that one entity is capable of handling, providing, or being compatible with one or more specified channels for communication, distribution, or operation.
- 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_69aed9484fb881909146f4c772ad277c |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03d7240c8190a64dcbc669772808 |
completed | March 9, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69af0183eb84819087d7184de28f5514 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:40 p.m.