Triple
T8488112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha CS-80 |
E200881
|
entity |
| Predicate | envelopeGenerators |
P49800
|
FINISHED |
| Object | ADSR envelopes |
—
|
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: ADSR envelopes | Statement: [Yamaha CS-80, envelopeGenerators, ADSR envelopes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: envelopeGenerators Context triple: [Yamaha CS-80, envelopeGenerators, ADSR envelopes]
-
A.
generators
Indicates that one entity produces, creates, or brings about another entity or outcome, typically as its source or origin.
-
B.
soundEngine
Indicates that one entity functions as or provides the sound engine (audio processing or synthesis system) used by another entity.
-
C.
signalGenerationMethod
chosen
Indicates the method or technique used to produce or generate a signal in a given context.
-
D.
audioModulation
Indicates a relationship where one audio signal or parameter is used to vary or control another audio signal’s characteristics (such as amplitude, frequency, or timbre) over time.
-
E.
synthesizerPlayer
Indicates that one entity plays or performs music using a synthesizer in relation to another entity or context.
- 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_69ca831d7b148190a6e32c1de43ab13b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe556b5188190b1124effd7445803 |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd107633c8190a36ba50e07876918 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:13 p.m.