Triple
T38599402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mozart–Da Ponte trilogy |
E934167
|
entity |
| Predicate | hasComposerLibrettistPair |
P206571
|
FINISHED |
| Object | Mozart–Da Ponte |
E934167
|
NE 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: Mozart–Da Ponte | Statement: [Mozart–Da Ponte trilogy, hasComposerLibrettistPair, Mozart–Da Ponte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComposerLibrettistPair Context triple: [Mozart–Da Ponte trilogy, hasComposerLibrettistPair, Mozart–Da Ponte]
-
A.
composerLibrettistSamePerson
Indicates that the composer of a musical or operatic work and its librettist are the same individual.
-
B.
hasLibrettistOccupation
Indicates that an entity’s occupation or professional role is that of a librettist.
-
C.
librettistOfWorkAppearingIn
Indicates that a person is the librettist responsible for the text of a work that appears within a larger composite work or collection.
-
D.
coAuthorOfLibrettoWith
Indicates that two or more individuals collaborated in writing the same libretto.
-
E.
hasComposerLyricistTeam
Indicates a relationship where a musical work is associated with a specific team that jointly fulfills the roles of composer and lyricist.
- F. None of above. chosen
Provenance (5 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_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4205b416f08190afaa2a093d9b1bc1 |
completed | June 29, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c85e308819083dd67b96f457659 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:32 p.m.