Triple
T22413346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In My Dreams |
E554046
|
entity |
| Predicate | singerVoiceType |
P135747
|
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: [In My Dreams, singerVoiceType, mezzo-soprano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: singerVoiceType Context triple: [In My Dreams, singerVoiceType, mezzo-soprano]
-
A.
voiceType
Indicates the specific vocal style, quality, or role associated with an entity’s voice in a given context.
-
B.
vocalGender
Indicates the perceived or assigned gender associated with an entity’s voice in a vocal performance or recording.
-
C.
hasMusicalVocalType
chosen
Indicates that an entity is associated with a specific type or classification of singing voice.
-
D.
singerVoiceActor
Indicates that the subject is both a singer and a voice actor for the object, or performs voice-acting roles in addition to singing in relation to the object.
-
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_69e11e4e6ce8819085a1e06d886bf21c |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1594496348190ba25dc0193d092f2 |
completed | April 29, 2026, 1:05 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
Created at: April 16, 2026, 8:46 p.m.