Triple
T37359290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deh vieni, non tardar |
E927535
|
entity |
| Predicate | characterRoleInOpera |
P148812
|
FINISHED |
| Object | Susanna |
—
|
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: Susanna | Statement: [Deh vieni, non tardar, characterRoleInOpera, Susanna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterRoleInOpera Context triple: [Deh vieni, non tardar, characterRoleInOpera, Susanna]
-
A.
operaActRole
Indicates the role or character that a performer portrays in a specific act of an opera.
-
B.
operaOrOratorioCharacterType
chosen
Indicates that the subject is a character type or role as it appears specifically within an opera or an oratorio.
-
C.
operaCharacterName
Indicates that the subject is the name (or names) of a character appearing in an opera.
-
D.
theaterRole
Indicates that an entity holds or performs a specific role or character in a theatrical production in relation to another entity (such as a play or performance).
-
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.
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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffe8ebe9fc8190b1934a3c4074370c |
completed | May 10, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_69ffe83a5de88190bed3e8bac86e8760 |
completed | May 10, 2026, 2:06 a.m. |
Created at: May 3, 2026, 4:16 p.m.