Triple
T37059823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zaira |
E917291
|
entity |
| Predicate | hasTitleRoleVoiceType |
P187769
|
FINISHED |
| Object | 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: soprano | Statement: [Zaira, hasTitleRoleVoiceType, soprano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleRoleVoiceType Context triple: [Zaira, hasTitleRoleVoiceType, soprano]
-
A.
sungByCharacterVoiceType
chosen
Indicates that a song or vocal part is performed by a character with a specified voice type (e.g., soprano, tenor, bass).
-
B.
voicedByAlsoKnownFor
Indicates that the person who voices a character is also notably recognized for another specific role or work.
-
C.
hasTitleRole
Indicates that an entity holds or is assigned a specific title or role in relation to another entity.
-
D.
musicalRole
Indicates the specific function or part an entity performs within a musical context, such as in a performance, composition, or ensemble.
-
E.
titleOrRole
Indicates that one entity serves as the title, position, or role held or described by another entity.
- 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_69f76e95fa40819091e14681087ae5e4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
Created at: May 3, 2026, 4:14 p.m.