Triple
T23568122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IV. Urlicht |
E580025
|
entity |
| Predicate | vocalPart |
P46281
|
FINISHED |
| Object | mezzo-soprano solo |
—
|
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: mezzo-soprano solo | Statement: [IV. Urlicht, vocalPart, mezzo-soprano solo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalPart Context triple: [IV. Urlicht, vocalPart, mezzo-soprano solo]
-
A.
hasVocalPartInMovement
Indicates that a vocal part is present and participates in a specific movement of a larger musical work.
-
B.
vocalConfiguration
Indicates how an entity’s vocal or sound-producing characteristics are arranged or specified in relation to another entity or context.
-
C.
hasNotableVocalType
chosen
Indicates that an entity is associated with a specific, noteworthy type or quality of vocalization or voice.
-
D.
vocalForm
Indicates the specific vocal or phonetic form in which something (such as a word, sound, or utterance) is expressed.
-
E.
vocal
Indicates that an entity produces or is characterized by audible sounds, speech, or vocalizations.
- 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_69e24601a9108190bc31e83833c980e4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1af6e11008190bdd28c3f85e3004e |
completed | April 29, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:35 p.m.