Triple
T29372139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OPM |
E744881
|
entity |
| Predicate | lfoWaveforms |
P39320
|
FINISHED |
| Object | multiple LFO 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 LFO waveforms | Statement: [OPM, lfoWaveforms, multiple LFO waveforms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lfoWaveforms Context triple: [OPM, lfoWaveforms, multiple LFO waveforms]
-
A.
waveformModel
Indicates that an entity serves as or uses a specific waveform model to represent or generate its signal behavior.
-
B.
numberOfWaves
Indicates the count of distinct wave events or oscillations associated with a given entity or interaction.
-
C.
waveType
chosen
Indicates the specific kind or category of wave associated with an entity or interaction (e.g., type of signal, motion, or oscillation).
-
D.
waveSource
Indicates that an entity serves as the origin or emitter of a wave affecting another entity or region.
-
E.
oscillatorsPerVoice
Indicates the number of oscillators assigned to or used by each individual voice in a multi-voice (polyphonic) system.
- 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_69f669ab36008190bc2e3c5dbdd2050d |
completed | May 2, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:28 p.m.