Triple
T30428495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony MDR-1AM2 |
E774096
|
entity |
| Predicate | supportsHighResolutionAudio |
P28700
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Sony MDR-1AM2, supportsHighResolutionAudio, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsHighResolutionAudio Context triple: [Sony MDR-1AM2, supportsHighResolutionAudio, yes]
-
A.
supportsHighDynamicRangeAudio
Indicates that an entity is capable of handling or providing audio with a high dynamic range, preserving a wide span between the quietest and loudest sounds.
-
B.
supportsAudioQuality
chosen
Indicates that one entity provides or is compatible with a specified level or type of audio quality for another entity or context.
-
C.
supportsDownmixing
Indicates that one entity can convert or mix multi-channel audio into a format with fewer channels (e.g., surround sound to stereo).
-
D.
supportsAudioEnhancement
Indicates that one entity provides or enables audio enhancement capabilities for another entity or process.
-
E.
supportsAutoLowLatencyMode
Indicates that the subject is capable of automatically enabling and managing a low-latency mode for its operations or interactions.
- 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:06 p.m.