Triple
T34792645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dandini |
E1002987
|
entity |
| Predicate | operaTypeOfWorkAppearsIn |
P202964
|
FINISHED |
| Object | dramma giocoso |
—
|
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: dramma giocoso | Statement: [Dandini, operaTypeOfWorkAppearsIn, dramma giocoso]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operaTypeOfWorkAppearsIn Context triple: [Dandini, operaTypeOfWorkAppearsIn, dramma giocoso]
-
A.
operaAct
Indicates that an entity performs in or takes part in an act (segment) of an opera performance.
-
B.
appearsInOperaBy
Indicates that one entity (typically a character, role, or element) is featured or takes part in an opera created or composed by another entity.
-
C.
associatedOpera
Indicates that there is a relationship linking an entity to an opera with which it is connected or related (e.g., as subject, inspiration, or context).
-
D.
operaActRole
Indicates the role or character that a performer portrays in a specific act of an opera.
-
E.
inOperaRepertoire
Indicates that a musical work is included as part of the standard or active repertoire performed in opera productions.
- 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a00d6aff0a08190a330dd0c7c1352f9 |
completed | May 10, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_6a00d60f2a508190aeaf5a9d8af9c39e |
completed | May 10, 2026, 7:01 p.m. |
| PDg | Predicate description generation | batch_6a00d6af4c588190a52f727a9dabd3dc |
completed | May 10, 2026, 7:04 p.m. |
Created at: May 3, 2026, 3:59 p.m.