Triple
T30383661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DTS Digital Surround |
E772892
|
entity |
| Predicate | audioCoding |
P53672
|
FINISHED |
| Object | perceptual coding |
—
|
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: perceptual coding | Statement: [DTS Digital Surround, audioCoding, perceptual coding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audioCoding Context triple: [DTS Digital Surround, audioCoding, perceptual coding]
-
A.
audioCodingType
chosen
Indicates the specific method or standard used to encode or compress an audio signal.
-
B.
audioCodecFamily
Indicates the general codec family or standard to which an audio codec belongs.
-
C.
audioStandard
Indicates the audio format or specification standard that applies to the associated media or device.
-
D.
audioTransmission
Indicates that an audio signal is being sent or conveyed from one entity (source) to another (destination) through some transmission medium or channel.
-
E.
relatedCodec
Indicates that one entity is associated with or corresponds to another through a shared or compatible codec used for encoding or decoding data.
- 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_69f2248e3444819081b05712dc6873de |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:01 p.m.