Triple
T32897439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act II Ride of the Valkyries |
E841513
|
entity |
| Predicate | premiereWorkPremiereCity |
P64741
|
FINISHED |
| Object | Munich |
—
|
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: Munich | Statement: [Act II Ride of the Valkyries, premiereWorkPremiereCity, Munich]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: premiereWorkPremiereCity Context triple: [Act II Ride of the Valkyries, premiereWorkPremiereCity, Munich]
-
A.
cityForPremieresOf
chosen
Indicates the city where premieres of a work, event, or production take place.
-
B.
premiereLocation
Indicates the place where something (such as a film, play, or event) is first publicly presented or debuted.
-
C.
premiereWithWork
Indicates that a performance, event, or production debuts at the same time as (or as part of) the first public presentation of a specific work.
-
D.
workPremiereTheater
Indicates the theater where a work (such as a play, film, or performance) was first publicly premiered.
-
E.
premiereFestivalEdition
Indicates the specific edition of a festival at which a work or event is first officially premiered.
- 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: May 1, 2026, 1:18 a.m.