Triple
T8488099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha CS-80 |
E200881
|
entity |
| Predicate | oscillatorsPerVoice |
P82996
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Yamaha CS-80, oscillatorsPerVoice, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oscillatorsPerVoice Context triple: [Yamaha CS-80, oscillatorsPerVoice, 2]
-
A.
typicalNumberOfVoices
Indicates the usual or characteristic number of distinct voices or parts involved in performing or realizing something (such as a musical work or texture).
-
B.
hasNumberOfAmplifierChannels
Indicates the relationship that specifies how many amplifier channels are present or supported in the associated entity.
-
C.
numberOfOrganPipes
Indicates the quantitative relationship specifying how many organ pipes are associated with a given organ or organ-related entity.
-
D.
soundFrequencyRange
Indicates the range of sound frequencies within which the related entity operates, is effective, or is characterized.
-
E.
numberOfWaves
Indicates the count of distinct wave events or oscillations associated with a given entity or interaction.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69cbe30d453481908f897ed2b06e7534 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:13 p.m.