Triple
T32742325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Der Einsame im Herbst |
E837248
|
entity |
| Predicate | premiereLocationWithCycle |
P3172
|
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: [Der Einsame im Herbst, premiereLocationWithCycle, Munich]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: premiereLocationWithCycle Context triple: [Der Einsame im Herbst, premiereLocationWithCycle, Munich]
-
A.
premiereLocation
chosen
Indicates the place where something (such as a film, play, or event) is first publicly presented or debuted.
-
B.
premiereState
Indicates the state or jurisdiction in which a work, event, or production first officially premieres.
-
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.
premiereSection
Indicates the specific program, segment, or section in which a work or performance is first publicly premiered.
-
E.
secondPartPremiereLocation
Indicates the location where the second part of something (such as a work, event, or series) first premiered or was initially presented.
- 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: May 1, 2026, 1:12 a.m.