Triple
T30303410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orest |
E770709
|
entity |
| Predicate | premiereLocationOfWorkAppearedIn |
P148813
|
FINISHED |
| Object | Dresden |
—
|
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: Dresden | Statement: [Orest, premiereLocationOfWorkAppearedIn, Dresden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: premiereLocationOfWorkAppearedIn Context triple: [Orest, premiereLocationOfWorkAppearedIn, Dresden]
-
A.
premiereLocation
Indicates the place where something (such as a film, play, or event) is first publicly presented or debuted.
-
B.
placeOfWorkPremiere
chosen
Indicates the location where a person’s work or performance was 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.
premieredInWorkPremiereYear
Indicates the year in which a work (such as a performance, film, or composition) had its first public premiere.
-
E.
premiereInstitution
Indicates that an entity had its first public showing, release, or debut at a particular institution or venue.
- 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 29, 2026, 7:49 p.m.