Triple
T29101414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha YMF276 |
E736647
|
entity |
| Predicate | supportsWaveforms |
P54328
|
FINISHED |
| Object | multiple selectable waveforms |
—
|
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: multiple selectable waveforms | Statement: [Yamaha YMF276, supportsWaveforms, multiple selectable waveforms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsWaveforms Context triple: [Yamaha YMF276, supportsWaveforms, multiple selectable waveforms]
-
A.
hasWaveShape
Indicates that one entity exhibits or possesses a particular wave-like geometric or physical shape in relation to another.
-
B.
waveformModel
Indicates that an entity serves as or uses a specific waveform model to represent or generate its signal behavior.
-
C.
hasWave
chosen
Indicates that one entity possesses, exhibits, or is associated with a particular wave or waveform.
-
D.
supportsPCM
Indicates that one entity is capable of handling, processing, or is compatible with PCM (Pulse-Code Modulation) audio data used by another entity.
-
E.
supportedInstrument
Indicates that an entity provides compatibility with, or operational support for, a specified instrument.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a0301c45274819083b0dd9d335f7ee0 |
completed | May 12, 2026, 10:32 a.m. |
| PD | Predicate disambiguation | batch_6a03015c272481908a7bfe81befb1764 |
completed | May 12, 2026, 10:30 a.m. |
Created at: April 28, 2026, 11:12 a.m.