Triple
T32902761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senta’s Ballad |
E841654
|
entity |
| Predicate | operaRoleContext |
P88989
|
FINISHED |
| Object | major solo for the heroine Senta |
—
|
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: major solo for the heroine Senta | Statement: [Senta’s Ballad, operaRoleContext, major solo for the heroine Senta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operaRoleContext Context triple: [Senta’s Ballad, operaRoleContext, major solo for the heroine Senta]
-
A.
operaStructureRole
chosen
Indicates the functional or narrative role that a structural element plays within an opera.
-
B.
operaActRole
Indicates the role or character that a performer portrays in a specific act of an opera.
-
C.
operaPremiereContext
Indicates the circumstances or setting (such as time, place, or event) in which an opera had its premiere performance.
-
D.
operaAct
Indicates that an entity performs in or takes part in an act (segment) of an opera performance.
-
E.
operaEnÁmbito
Indicates that an entity operates, functions, or carries out its activities within a specified domain, field, or scope.
- 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_69f34946a5208190bbd79f0fec4323bd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a003ffb548081908ba64fd2b570f42f |
completed | May 10, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_6a003fcecf788190a13dff38b9de3414 |
completed | May 10, 2026, 8:20 a.m. |
Created at: May 1, 2026, 1:19 a.m.