Triple
T37847981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falstaff (libretto) |
E943957
|
entity |
| Predicate | intendedGenreOfOpera |
P80490
|
FINISHED |
| Object | commedia lirica |
—
|
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: commedia lirica | Statement: [Falstaff (libretto), intendedGenreOfOpera, commedia lirica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedGenreOfOpera Context triple: [Falstaff (libretto), intendedGenreOfOpera, commedia lirica]
-
A.
tipoDiOpera
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.
operaGenre
chosen
Indicates that an opera belongs to or is categorized under a particular musical or dramatic genre.
-
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.
operaAct
Indicates that an entity performs in or takes part in an act (segment) of an opera performance.
-
E.
theatricalGenre
Indicates the specific theatrical genre or style to which a performance, play, or production belongs.
- 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_69f76eed4d9c81908b1b71ba9e3b61fe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe629b4fa481908467c7c41b77f0c6 |
completed | May 8, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69fe61bb260c819083f9378a3a06ca47 |
completed | May 8, 2026, 10:20 p.m. |
Created at: May 3, 2026, 4:19 p.m.