Triple
T33595690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dreikönigskirche (Dresden) |
E860557
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cultural heritage monument in Dresden |
C54435
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: cultural heritage monument in Dresden Context triple: [Dreikönigskirche (Dresden), instanceOf, cultural heritage monument in Dresden]
-
A.
landmark in Dresden
chosen
A landmark in Dresden is a notable, historically or culturally significant site or structure within the city that serves as a recognizable point of reference for residents and visitors.
-
B.
Landmark in Meissen
A "Landmark in Meissen" represents any notable, historically or culturally significant site, structure, or natural feature within the city of Meissen that serves as a recognizable point of reference or attraction.
-
C.
cultural heritage monument in Berlin
A cultural heritage monument in Berlin is a legally protected building, site, or structure recognized for its historical, architectural, or cultural significance within the city’s heritage conservation framework.
-
D.
museum building in Germany
A museum building in Germany is a purpose-built or repurposed structure located within German territory that houses, preserves, and publicly exhibits collections of cultural, historical, artistic, or scientific significance.
-
E.
building in Munich
A building in Munich is a constructed structure within the city of Munich, Germany, serving residential, commercial, cultural, or administrative purposes and reflecting the region’s architectural styles and urban context.
- F. None of above.
Provenance (1 batch)
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_69f3497f35908190a2e9bbb9b96c7a3f |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:41 a.m.