Triple
T9175808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DTS-HD Master Audio |
E220195
|
entity |
| Predicate | supportsSpeakerLayouts |
P62625
|
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: [DTS-HD Master Audio, supportsSpeakerLayouts, 5.1 surround sound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSpeakerLayouts Context triple: [DTS-HD Master Audio, supportsSpeakerLayouts, 5.1 surround sound]
-
A.
supportsSpeakerPlacement
Indicates that one entity provides a suitable location or structure for positioning or mounting a speaker.
-
B.
hasSpeakerType
Indicates that an entity functions in a particular role or category as a speaker (e.g., narrator, character, announcer) within a given context.
-
C.
supportsSpatialAudioWith
chosen
Indicates that one entity is compatible with and can provide or enable spatial audio functionality when used with another entity.
-
D.
supportsMultiRoomAudio
Indicates that the subject is capable of playing synchronized audio across multiple rooms or speakers simultaneously.
-
E.
driveLayoutSupported
Indicates that a particular drive layout or configuration is compatible with and can be correctly handled 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.