Triple
T7998678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marienkirche (Berlin) |
E186190
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | landmark 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: landmark in Berlin Context triple: [Marienkirche (Berlin), instanceOf, landmark in Berlin]
-
A.
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.
-
B.
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.
-
C.
Berlin Wall museum
A Berlin Wall museum is a cultural institution dedicated to preserving, exhibiting, and interpreting artifacts, stories, and historical context related to the Berlin Wall and its impact on Germany and the world.
-
D.
Berlin U-Bahn station
A Berlin U-Bahn station is an underground or elevated public transit facility in Berlin that serves as a stop for the city’s metro trains, providing passenger access, ticketing, and connections to other transport modes.
-
E.
quarter of Berlin
A quarter of Berlin is an administrative district within the city that encompasses a distinct neighborhood with its own local character, infrastructure, and community life.
- 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_69ca82aaaf24819084b94d18f699ba53 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:17 p.m.