Triple
T29372137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OPM |
E744881
|
entity |
| Predicate | envelopeGenerator |
P82800
|
FINISHED |
| Object | ADSR-type envelope |
—
|
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: ADSR-type envelope | Statement: [OPM, envelopeGenerator, ADSR-type envelope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: envelopeGenerator Context triple: [OPM, envelopeGenerator, ADSR-type envelope]
-
A.
hasEnvelopeGenerator
chosen
Indicates that an entity possesses or is associated with an envelope generator component that shapes the evolution of a signal or parameter over time.
-
B.
launchEnvelope
Indicates initiating the sending or dispatching of an item or message, typically by packaging it into an envelope and starting its delivery process.
-
C.
enveloped
Indicates that one entity is completely or largely surrounded, covered, or enclosed by another.
-
D.
engagementEnvelope
Indicates the spatial or contextual bounds within which an interaction, operation, or engagement between entities is valid or permitted.
-
E.
envelopeShapes
Indicates a relationship where one entity defines or determines the geometric or boundary shape(s) that enclose or outline another entity.
- 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.