Triple
T26023435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tsar’s Bride |
E647215
|
entity |
| Predicate | hasMezzoSopranoRole |
P172762
|
FINISHED |
| Object | Lyubasha |
—
|
NE NERFINISHED |
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: Lyubasha | Statement: [The Tsar’s Bride, hasMezzoSopranoRole, Lyubasha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMezzoSopranoRole Context triple: [The Tsar’s Bride, hasMezzoSopranoRole, Lyubasha]
-
A.
sopranoRolePerformed
Indicates that an entity has performed a role written for a soprano voice in a musical or operatic work.
-
B.
notableSopranoRole
Indicates that the object is a soprano role for which the subject is particularly well known or distinguished.
-
C.
notableLyricSopranoRole
Indicates that the subject is notably recognized for performing the specified lyric soprano role.
-
D.
sungByRole
Indicates that a song or musical piece is performed vocally by an entity in a specific role (e.g., lead singer, backing vocalist).
-
E.
musicalRole
Indicates the specific function or part an entity performs within a musical context, such as in a performance, composition, or ensemble.
- F. None of above. chosen
Provenance (4 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 22, 2026, 9:05 a.m.