Triple
T3078571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dolby Digital |
E64199
|
entity |
| Predicate | supportsChannelConfiguration |
P203
|
FINISHED |
| Object | mono |
—
|
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: mono | Statement: [Dolby Digital, supportsChannelConfiguration, mono]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsChannelConfiguration Context triple: [Dolby Digital, supportsChannelConfiguration, mono]
-
A.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
B.
supportsBuyingChannel
Indicates that one entity enables, allows, or is compatible with a particular buying or purchasing channel used by another entity.
-
C.
supportsPlugAndPlayLikeConfiguration
Indicates that one entity enables another to be configured in a plug-and-play–like manner, requiring minimal manual setup or integration effort.
-
D.
hasCanalOrChannel
Indicates that one entity possesses, contains, or is traversed by a canal or channel that serves as a conduit or passageway.
-
E.
supportedAs
Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of another entity.
- 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_69ad857bb4c88190a4cf27893fcabed8 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada1a86a848190a47ca127cc7e6326 |
completed | March 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69ad9debb6308190be28378ae1fc98af |
completed | March 8, 2026, 4:03 p.m. |
Created at: March 8, 2026, 3:02 p.m.