Triple
T8602850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha YM2151 |
E203720
|
entity |
| Predicate | hasModulationFeatures |
P48651
|
FINISHED |
| Object | LFO |
—
|
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: LFO | Statement: [Yamaha YM2151, hasModulationFeatures, LFO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModulationFeatures Context triple: [Yamaha YM2151, hasModulationFeatures, LFO]
-
A.
usesModulation
Indicates that one entity applies or employs a particular modulation method or scheme in relation to another entity or process.
-
B.
hasAudioFeature
chosen
Indicates that one entity possesses or is associated with a specific audio-related characteristic or property.
-
C.
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.
-
D.
hasNoiseModes
Indicates that an entity supports or is associated with one or more distinct noise-related operating modes or settings.
-
E.
usesHarmonics
Indicates that one entity employs harmonic frequencies or overtones of another entity or signal as part of its operation or behavior.
- 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_69ca832b56948190ba751cec255308f1 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46dc23448190a5eb63455578427e |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454eb2908190acf0e4336bc67e7b |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:24 p.m.