Triple
T38599390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mozart–Da Ponte trilogy |
E934167
|
entity |
| Predicate | secondOpera |
P62306
|
FINISHED |
| Object | Don Giovanni |
—
|
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: Don Giovanni | Statement: [Mozart–Da Ponte trilogy, secondOpera, Don Giovanni]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondOpera Context triple: [Mozart–Da Ponte trilogy, secondOpera, Don Giovanni]
-
A.
secondOperation
Indicates that an entity participates in or is associated with a subsequent or secondary operation relative to a primary one.
-
B.
thirdOpera
Indicates that one entity is the third opera created, performed, or associated within a sequence or body of work related to the other entity.
-
C.
secondElement
chosen
Indicates that one entity is the second element in an ordered pair, sequence, or collection relative to another entity.
-
D.
secondAct
Indicates that an entity performs, participates in, or is associated with the second act or phase within a larger, ordered sequence of actions or events.
-
E.
secondSeries
Indicates that one entity is the second installment or season in a series relative to another entity.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffebbd9bac8190b3dca4b7252a2278 |
completed | May 10, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_69ffe93120a08190a44bb64d052eda78 |
completed | May 10, 2026, 2:10 a.m. |
Created at: May 3, 2026, 4:32 p.m.