Triple
T37381213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papagena |
E928435
|
entity |
| Predicate | associatedWorkLibrettist |
P134607
|
FINISHED |
| Object | Emanuel Schikaneder |
E927500
|
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: Emanuel Schikaneder | Statement: [Papagena, associatedWorkLibrettist, Emanuel Schikaneder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWorkLibrettist Context triple: [Papagena, associatedWorkLibrettist, Emanuel Schikaneder]
-
A.
librettistOfWorkAppearingIn
Indicates that a person is the librettist responsible for the text of a work that appears within a larger composite work or collection.
-
B.
librettistOfParentWork
Indicates that one entity is the librettist who wrote the text (libretto) for the parent work associated with another entity.
-
C.
librettistOfOpera
chosen
Indicates that one entity is the librettist who wrote the text (libretto) for the specified opera.
-
D.
coAuthorOfLibrettoWith
Indicates that two or more individuals collaborated in writing the same libretto.
-
E.
principalLibrettist
Indicates that one entity serves as the main librettist responsible for writing the text of a musical or operatic work for another entity.
- F. None of above.
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_69f76eb9e66881908534cf22d04c3b5a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41541c365c8190ac2281d7e811a7bf |
completed | June 28, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.