Triple
T14405336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U-Bahnhof Seestraße |
E357181
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Verkehrsbauwerk in Berlin |
C33941
|
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: Verkehrsbauwerk in Berlin Context triple: [U-Bahnhof Seestraße, instanceOf, Verkehrsbauwerk 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.
road in Berlin
A road in Berlin is a public thoroughfare within the city’s urban network that facilitates vehicular, bicycle, and pedestrian movement while integrating with Berlin’s historical layout, public transit, and zoning infrastructure.
-
C.
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.
-
D.
section of the Berlin Wall
A section of the Berlin Wall is a preserved or reconstructed fragment of the former fortified barrier that once divided East and West Berlin, serving as a historical artifact and symbol of Cold War division and reunification.
-
E.
sector of Berlin
A sector of Berlin is a geographically defined administrative or historical subdivision of the city, often reflecting political, economic, or cultural distinctions within the urban area.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:17 a.m.