Triple
T33804337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martenot waves |
E866338
|
entity |
| Predicate | volumeControlMethod |
P167951
|
FINISHED |
| Object | pressure-sensitive control |
—
|
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: pressure-sensitive control | Statement: [Martenot waves, volumeControlMethod, pressure-sensitive control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: volumeControlMethod Context triple: [Martenot waves, volumeControlMethod, pressure-sensitive control]
-
A.
supportsVolumeControl
Indicates that one entity provides the capability to adjust or manage the audio volume level of another entity.
-
B.
audioControlMethod
chosen
Indicates the method or mechanism by which audio playback or volume is controlled.
-
C.
volumeLevels
Indicates the relative loudness or intensity settings assigned to one or more entities or audio outputs.
-
D.
hasSpeechLevels
Indicates that a language, dialect, or communicative system distinguishes different levels or styles of speech used according to social context, formality, or relative status between speakers.
-
E.
reporterVolume
Indicates the amount or intensity of content produced or reported by a reporter within a given context or period.
- 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_69f3499057fc81909d862b1309a3bd71 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbd04e081909fffd6476f43f9b8 |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:46 a.m.