Triple
T37359319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deh vieni, non tardar |
E927535
|
entity |
| Predicate | workTypeOfOpera |
P168726
|
FINISHED |
| Object | opera buffa |
—
|
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: opera buffa | Statement: [Deh vieni, non tardar, workTypeOfOpera, opera buffa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workTypeOfOpera Context triple: [Deh vieni, non tardar, workTypeOfOpera, opera buffa]
-
A.
tipoDiOpera
chosen
Indicates that one entity is classified as a specific type or category of work (e.g., artwork, project, or production) in relation to another entity.
-
B.
musicalTheatreWorkType
Indicates the specific type or category of a musical theatre work that characterizes the nature of the production.
-
C.
operaAct
Indicates that an entity performs in or takes part in an act (segment) of an opera performance.
-
D.
operaActRole
Indicates the role or character that a performer portrays in a specific act of an opera.
-
E.
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).
- 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_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.