Triple
T33465388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | What's Opera, Doc? |
E857028
|
entity |
| Predicate | parodiesWorkBy |
P174533
|
FINISHED |
| Object | Richard Wagner |
—
|
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: Richard Wagner | Statement: [What's Opera, Doc?, parodiesWorkBy, Richard Wagner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parodiesWorkBy Context triple: [What's Opera, Doc?, parodiesWorkBy, Richard Wagner]
-
A.
parodies
Indicates that one entity imitates another in an exaggerated or humorous way, often to criticize or comment on the original.
-
B.
satirizedBy
Indicates that the subject is the target or object of satire created or performed by the specified entity.
-
C.
isHumorousWork
Indicates that a work is intended to be humorous or comedic in nature.
-
D.
parodySourceAuthor
chosen
Indicates that the subject is the author or creator of the original work that is being parodied by the object.
-
E.
alliedWithParodies
Indicates that one entity forms an alliance or cooperative association with another entity specifically in the context of creating, supporting, or engaging in parodies.
- 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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e4f996948190a20e96059d5188cc |
completed | May 3, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:37 a.m.