Triple
T38599572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don Alfonso |
E934171
|
entity |
| Predicate | appearsInWorkWithLibrettoBy |
P198818
|
FINISHED |
| Object | Lorenzo Da Ponte |
—
|
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: Lorenzo Da Ponte | Statement: [Don Alfonso, appearsInWorkWithLibrettoBy, Lorenzo Da Ponte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInWorkWithLibrettoBy Context triple: [Don Alfonso, appearsInWorkWithLibrettoBy, Lorenzo Da Ponte]
-
A.
hasLibrettoIn
Indicates that a musical or operatic work has its libretto written in a specified language.
-
B.
librettoBy
Indicates that a work’s libretto (the text of an opera or similar vocal work) was written by a particular person.
-
C.
includesLibretto
Indicates that one entity (typically a musical or operatic work or publication) contains or is accompanied by the full text/libretto of another work.
-
D.
hasLibrettoPublication
Indicates that a work is associated with a specific published version of its libretto.
-
E.
librettistOfWorkAppearingIn
Indicates that a person is the librettist responsible for the text of a work that appears within a larger composite work or collection.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff0b6bc4a88190bf1d38c6ea26bcdc |
completed | May 9, 2026, 10:24 a.m. |
| PD | Predicate disambiguation | batch_69ff082a22f4819095ded971dbd8ea7b |
completed | May 9, 2026, 10:10 a.m. |
| PDg | Predicate description generation | batch_69ff0b6a541c8190a6fa847552f3491f |
completed | May 9, 2026, 10:24 a.m. |
Created at: May 3, 2026, 4:32 p.m.