Triple
T25768693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yours |
E648955
|
entity |
| Predicate | hasNotableVocalCharacteristics |
P29850
|
FINISHED |
| Object | melismatic passages |
—
|
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: melismatic passages | Statement: [Yours, hasNotableVocalCharacteristics, melismatic passages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableVocalCharacteristics Context triple: [Yours, hasNotableVocalCharacteristics, melismatic passages]
-
A.
hasNotableVocalType
Indicates that an entity is associated with a specific, noteworthy type or quality of vocalization or voice.
-
B.
hasMusicalVocalType
Indicates that an entity is associated with a specific type or classification of singing voice.
-
C.
hasVocals
Indicates that the subject includes or features vocal elements, such as singing or spoken voice, rather than being purely instrumental or non-vocal.
-
D.
vocalizationCharacteristic
chosen
Indicates how an entity’s vocal sounds are characterized, such as their quality, style, or distinctive acoustic features.
-
E.
hasVocalCharacter
Indicates that an entity possesses a particular vocal quality, style, or characteristic in its sound or voice.
- 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_69e7ab322db0819092d6a2b3d4572e01 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: April 22, 2026, 5:13 a.m.