Triple
T24851243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belvedere tea house |
E621893
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | building in Berlin |
C18071
|
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: building in Berlin Context triple: [Belvedere tea house, instanceOf, building in Berlin]
-
A.
skyscraper in Berlin
A skyscraper in Berlin is a tall, multi-story commercial or mixed-use building that rises prominently above the city’s predominantly mid-rise skyline, integrating modern architecture with the urban fabric and historical context of the German capital.
-
B.
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.
-
C.
cultural heritage monument in Berlin
chosen
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.
Verkehrsbauwerk in Berlin
A "Verkehrsbauwerk in Berlin" is a transportation-related structure within the city of Berlin, such as bridges, tunnels, stations, or other built facilities that support and organize traffic flow.
-
E.
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.
- 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_69e2fac297e481909d3aedc75f585e42 |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 5:20 a.m.