Triple
T29372287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha DX-series synthesizer technology |
E744884
|
entity |
| Predicate | operatorWaveform |
P39320
|
FINISHED |
| Object | sine wave |
—
|
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: sine wave | Statement: [Yamaha DX-series synthesizer technology, operatorWaveform, sine wave]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorWaveform Context triple: [Yamaha DX-series synthesizer technology, operatorWaveform, sine wave]
-
A.
waveformModel
Indicates that an entity serves as or uses a specific waveform model to represent or generate its signal behavior.
-
B.
waveType
chosen
Indicates the specific kind or category of wave associated with an entity or interaction (e.g., type of signal, motion, or oscillation).
-
C.
hasWaveShape
Indicates that one entity exhibits or possesses a particular wave-like geometric or physical shape in relation to another.
-
D.
waveUse
Indicates the use or application of a wave (or wave-based phenomenon) by one entity in relation to another entity or context.
-
E.
waveSource
Indicates that an entity serves as the origin or emitter of a wave affecting another entity or region.
- 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69ff109695008190a22b47ef8be2e3f9 |
completed | May 9, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69ff0f243ea88190970d2c520b55c816 |
completed | May 9, 2026, 10:40 a.m. |
Created at: April 28, 2026, 2:28 p.m.