Triple
T29035564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha YM2203 |
E737848
|
entity |
| Predicate | supportsAmplitudeModulation |
—
|
GENERATED |
| Object | yes |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAmplitudeModulation Context triple: [Yamaha YM2203, supportsAmplitudeModulation, yes]
-
A.
usesModulation
Indicates that one entity applies or employs a particular modulation method or scheme in relation to another entity or process.
-
B.
modulationCapabilities
chosen
Indicates the types or methods of signal modulation that an entity can perform or support.
-
C.
hasAmplifier
Indicates that one entity functions as an amplifier for another entity, enhancing or boosting its signal, power, or effect.
-
D.
hasNoiseFrequencyControl
Indicates that an entity provides a control or setting to adjust the frequency characteristics of noise.
-
E.
supportsPCM
Indicates that one entity is capable of handling, processing, or is compatible with PCM (Pulse-Code Modulation) audio data used by another entity.
- F. None of above.
Provenance (1 batch)
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. |
Created at: April 28, 2026, 9:58 a.m.