Triple
T35281341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memorymoog |
E1018940
|
entity |
| Predicate | envelopesPerVoice |
P182685
|
FINISHED |
| Object | 2 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: 2 ADSR envelopes | Statement: [Memorymoog, envelopesPerVoice, 2 ADSR envelopes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: envelopesPerVoice Context triple: [Memorymoog, envelopesPerVoice, 2 ADSR envelopes]
-
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.
enveloped
Indicates that one entity is completely or largely surrounded, covered, or enclosed by another.
-
C.
hasEnvelopeShapes
Indicates that one entity possesses or is characterized by specific envelope-like shapes associated with another entity.
-
D.
envelopeShapes
Indicates a relationship where one entity defines or determines the geometric or boundary shape(s) that enclose or outline another entity.
-
E.
hasVoices
Indicates that an entity possesses or includes one or more vocal parts, voice tracks, or spoken/sung voice elements.
- 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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7904a770481908ef3f788e51e8dba |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78f629d508190b755848162c4e101 |
completed | May 3, 2026, 6:09 p.m. |
Created at: May 3, 2026, 4:03 p.m.