Triple
T31613545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nero (opera) |
E806691
|
entity |
| Predicate | composerOtherWorks |
P60820
|
FINISHED |
| Object | The Demon (opera) |
—
|
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: The Demon (opera) | Statement: [Nero (opera), composerOtherWorks, The Demon (opera)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: composerOtherWorks Context triple: [Nero (opera), composerOtherWorks, The Demon (opera)]
-
A.
composerOtherNotableWorks
chosen
Indicates that a composer has other notable musical works beyond the primary one currently being referenced.
-
B.
composerOfRelatedWorks
Indicates that an entity is the composer of works that are related to another specified work or set of works.
-
C.
worksBy
Indicates that one entity is the creator or author of a work (such as a book, artwork, or composition) associated with another entity.
-
D.
workByAuthorAlsoKnownFor
Indicates that a work is created by an author who is also notably recognized for another specified work or contribution.
-
E.
hasAuthorOfOtherWork
Indicates that an entity is the author of another distinct work associated with the first 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: April 30, 2026, 10:37 p.m.