Triple
T8715052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peterskirche (St Peter’s Church) |
E206872
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | building in Munich |
C24949
|
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 Munich Context triple: [Peterskirche (St Peter’s Church), instanceOf, building in Munich]
-
A.
museum in Munich
A museum in Munich is a cultural institution located within the city that collects, preserves, researches, and exhibits artworks, artifacts, or historical objects for public education and enjoyment.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
city square in Germany
A city square in Germany is a central public open space, often surrounded by historic buildings, shops, and cafes, serving as a focal point for social, cultural, and civic activities.
- 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:35 p.m.