Triple
T29035564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha YM2203 |
E737848
|
entity |
| Predicate | supportsAmplitudeModulation |
P167009
|
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: [Yamaha YM2203, supportsAmplitudeModulation, yes]
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 (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_6a02ff7de1d881909c29729f2a771381 |
completed | May 12, 2026, 10:22 a.m. |
| PD | Predicate disambiguation | batch_6a02fd1c45c48190bf9dbd91acaeee9f |
completed | May 12, 2026, 10:12 a.m. |
Created at: April 28, 2026, 9:58 a.m.