Triple
T17055347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Congress Hall |
E413805
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | landmark in Nuremberg |
C38717
|
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 Nuremberg Context triple: [Congress Hall, instanceOf, landmark in Nuremberg]
-
A.
district of Nuremberg
A district of Nuremberg is an administrative subdivision of the city that encompasses specific neighborhoods, local governance functions, and community services within its defined boundaries.
-
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.
landmark of Frankfurt am Main
A landmark of Frankfurt am Main is a prominent, widely recognized site or structure within the city that holds cultural, historical, architectural, or symbolic significance and serves as a key point of orientation or identity for residents and visitors.
-
D.
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.
-
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. 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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:34 a.m.