Triple
T31908931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orfeo ed Euridice |
E814627
|
entity |
| Predicate | modernOrfeoVoiceType |
P2000
|
FINISHED |
| Object | mezzo-soprano |
—
|
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 | Statement: [Orfeo ed Euridice, modernOrfeoVoiceType, mezzo-soprano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernOrfeoVoiceType Context triple: [Orfeo ed Euridice, modernOrfeoVoiceType, mezzo-soprano]
-
A.
voiceTypeOfOroe
Indicates that an entity represents the specific type or classification of voice associated with Oroe.
-
B.
voiceType
chosen
Indicates the specific vocal style, quality, or role associated with an entity’s voice in a given context.
-
C.
hasVoices
Indicates that an entity possesses or includes one or more vocal parts, voice tracks, or spoken/sung voice elements.
-
D.
premiereVoiceType
Indicates the primary or leading vocal classification associated with a performance, role, or work.
-
E.
vocalConfiguration
Indicates how an entity’s vocal or sound-producing characteristics are arranged or specified in relation to another entity or context.
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 1, 2026, 12:01 a.m.