Triple
T12935158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dolby S |
E309488
|
entity |
| Predicate | intendedQualityLevel |
P99246
|
FINISHED |
| Object | near-CD-quality 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: near-CD-quality sound | Statement: [Dolby S, intendedQualityLevel, near-CD-quality sound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedQualityLevel Context triple: [Dolby S, intendedQualityLevel, near-CD-quality sound]
-
A.
impliesQualityLevel
chosen
Indicates that one entity entails, suggests, or leads to a particular quality level in another entity or outcome.
-
B.
storageQuality
Indicates the degree or standard of how well something is stored, such as its preservation, safety, or suitability for use.
-
C.
requiresQuality
Indicates that one entity depends on or needs another entity to possess a specific quality or attribute in order for a condition, action, or relationship to hold.
-
D.
hasPerceptualQuality
Indicates that something possesses a particular sensory or perceptual characteristic, such as a color, sound, texture, taste, or smell.
-
E.
imageQuality
Indicates the assessed level or degree of visual clarity, detail, and overall fidelity of an image.
- 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97db69f548190a1a693bc0d6c191a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:42 p.m.