Triple
T22718278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melisso |
E561791
|
entity |
| Predicate | operaType |
P80490
|
FINISHED |
| Object | opera seria |
—
|
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 seria | Statement: [Melisso, operaType, opera seria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operaType Context triple: [Melisso, operaType, opera seria]
-
A.
operaGenre
chosen
Indicates that an opera belongs to or is categorized under a particular musical or dramatic genre.
-
B.
operaAct
Indicates that an entity performs in or takes part in an act (segment) of an opera performance.
-
C.
operaNumberType
Indicates the type or classification assigned to an opera’s identifying number within a cataloging or numbering system.
-
D.
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).
-
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_69e2454fc984819088213b58ee87a002 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1790ecbc48190926d16b20b674dbd |
completed | April 29, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69ee62c24a1c819096c410906e9b173c |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:19 p.m.