Triple
T28684350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of Our Lady (Dresden) |
E726089
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | landmark 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: landmark in Dresden Context triple: [Church of Our Lady (Dresden), instanceOf, landmark in Dresden]
-
A.
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.
-
B.
landmark in Lübeck
A landmark in Lübeck is a notable physical site, building, or monument within the city that holds historical, cultural, architectural, or social significance and serves as a recognizable point of reference for residents and visitors.
-
C.
landmark in Nuremberg
A landmark in Nuremberg is a notable physical site or structure within the city—such as a historic building, monument, square, or cultural institution—that holds significant historical, architectural, or cultural importance and serves as a recognizable point of reference for residents and visitors.
-
D.
landmark in Stralsund
A landmark in Stralsund is a notable, historically or culturally significant site or structure within the city that serves as a recognizable point of interest for residents and visitors.
-
E.
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.
- F. None of above. chosen
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_69f01d867608819086bc3e6b4f9de866 |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 5:11 a.m.