Triple
T32897353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ride of the Valkyries |
E841511
|
entity |
| Predicate | notableUseInAnimation |
P55029
|
FINISHED |
| Object | What’s Opera, Doc? |
E857028
|
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: What’s Opera, Doc? | Statement: [Ride of the Valkyries, notableUseInAnimation, What’s Opera, Doc?]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableUseInAnimation Context triple: [Ride of the Valkyries, notableUseInAnimation, What’s Opera, Doc?]
-
A.
notableUse
Indicates that something is prominently or famously used by a particular entity, context, or for a specific purpose.
-
B.
notableAppearanceIn
chosen
Indicates that an entity is prominently featured or plays a significant role in a particular work, event, or context.
-
C.
usedInClosingCreditsOf
Indicates that something is listed or acknowledged in the closing credits of a work (such as a film, show, or game).
-
D.
mentionedInFilm
Indicates that an entity is referenced or talked about within the content of a film.
-
E.
usedInProductionOfFilm
Indicates that something (such as a resource, tool, or material) was utilized during the making or production process of a film.
- 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34c68e7bb081909724527bfdb2df35 |
completed | June 19, 2026, 4:33 a.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:18 a.m.