Triple
T9175824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DTS-HD Master Audio |
E220195
|
entity |
| Predicate | audioChannelEncoding |
P53672
|
FINISHED |
| Object | PCM-based lossless reconstruction |
—
|
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: PCM-based lossless reconstruction | Statement: [DTS-HD Master Audio, audioChannelEncoding, PCM-based lossless reconstruction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audioChannelEncoding Context triple: [DTS-HD Master Audio, audioChannelEncoding, PCM-based lossless reconstruction]
-
A.
audioCodingType
chosen
Indicates the specific method or standard used to encode or compress an audio signal.
-
B.
audioStandard
Indicates the audio format or specification standard that applies to the associated media or device.
-
C.
audioChannels
Indicates the number or configuration of distinct audio signal paths (such as mono, stereo, or surround) used in a recording, transmission, or playback.
-
D.
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.
-
E.
audioFormatSupported
Indicates that a particular audio format is recognized and can be correctly processed or played by a given system or component.
- 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_69ca83e589948190ac9907819db11ddf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccbfa496548190a096969eebf732f3 |
completed | April 1, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69cc660761d88190ab6134b43b376964 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:23 p.m.