Triple
T30726510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DTS, Inc. |
E782291
|
entity |
| Predicate | surroundSoundChannelSupport |
P170073
|
FINISHED |
| Object | 5.1-channel audio |
—
|
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-channel audio | Statement: [DTS, Inc., surroundSoundChannelSupport, 5.1-channel audio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surroundSoundChannelSupport Context triple: [DTS, Inc., surroundSoundChannelSupport, 5.1-channel audio]
-
A.
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.
-
B.
stereoCapability
Indicates that an entity has the ability to produce, process, or support stereo (two-channel) audio.
-
C.
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.
-
D.
hasLFEChannels
Indicates that an entity includes or is associated with one or more Low-Frequency Effects (LFE) audio channels.
-
E.
supportsSpatialAudioWith
Indicates that one entity is compatible with and can provide or enable spatial audio functionality when used with 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68c5e18608190b3b2d8dc10023ec8 |
completed | May 2, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 29, 2026, 8:36 p.m.