Triple
T32204054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dinorah |
E822621
|
entity |
| Predicate | vocalTypeOfTitleRole |
P174640
|
FINISHED |
| Object | coloratura 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: coloratura soprano | Statement: [Dinorah, vocalTypeOfTitleRole, coloratura soprano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalTypeOfTitleRole Context triple: [Dinorah, vocalTypeOfTitleRole, coloratura soprano]
-
A.
musicalRole
Indicates the specific function or part an entity performs within a musical context, such as in a performance, composition, or ensemble.
-
B.
sungByRole
Indicates that a song or musical piece is performed vocally by an entity in a specific role (e.g., lead singer, backing vocalist).
-
C.
sopranoRole
chosen
Indicates that an entity is a role or part in a work that is intended to be performed by a soprano voice.
-
D.
notableLyricSopranoRole
Indicates that the subject is notably recognized for performing the specified lyric soprano role.
-
E.
sopranoRolePerformed
Indicates that an entity has performed a role written for a soprano voice in a musical or operatic work.
- 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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 12:36 a.m.