Triple
T29035587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha YM2203 |
E737848
|
entity |
| Predicate | supportsStereo |
P82801
|
FINISHED |
| Object | no (mono output on-chip) |
—
|
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: no (mono output on-chip) | Statement: [Yamaha YM2203, supportsStereo, no (mono output on-chip)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsStereo Context triple: [Yamaha YM2203, supportsStereo, no (mono output on-chip)]
-
A.
stereoCapability
Indicates that an entity has the ability to produce, process, or support stereo (two-channel) audio.
-
B.
supportsStereoPairing
Indicates that an entity is capable of being paired with another similar entity to function together as a synchronized stereo audio system.
-
C.
hasStereoOutput
chosen
Indicates that an entity provides or supports audio output in stereo (two-channel) format.
-
D.
supportsStereoFMRadio
Indicates that the subject device is capable of receiving and playing stereo FM radio broadcasts.
-
E.
stereoConfiguration
Indicates how multiple audio channels are arranged and related to each other in a stereo sound setup.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a03008316dc8190a9f6faf48d25a4f8 |
completed | May 12, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_6a030023e66881909ea79f1365ab538a |
completed | May 12, 2026, 10:25 a.m. |
Created at: April 28, 2026, 9:58 a.m.