Triple
T38293281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dolby noise reduction family |
E1022420
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | audio signal processing system family |
C56798
|
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: audio signal processing system family Context triple: [Dolby noise reduction family, instanceOf, audio signal processing system family]
-
A.
audio signal processing software
Audio signal processing software is a class of applications that analyze, modify, and generate audio signals through digital algorithms for tasks such as filtering, enhancement, synthesis, and effects processing.
-
B.
3D audio processing hardware
Specialized electronic devices that capture, process, and output spatially accurate sound fields in real time to create immersive three-dimensional audio experiences.
-
C.
audio coding standard family
An audio coding standard family is a group of related specifications that define how digital audio is compressed, encoded, transmitted, and decoded to balance quality, bitrate, and compatibility across devices and applications.
-
D.
audio hardware architecture
Audio hardware architecture is the conceptual design and organization of components and signal paths that capture, process, convert, route, and output audio within an electronic system.
-
E.
audio compression codec family
chosen
A family of audio compression codecs is a group of related encoding and decoding algorithms designed to reduce the size of digital audio data while preserving sound quality according to shared technical principles or standards.
- 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_69f76df190f081908d5aa02c8a9286d0 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.