Triple
T31550182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamminiemi, Helsinki |
E804976
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | building in Helsinki |
C58356
|
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 Helsinki Context triple: [Tamminiemi, Helsinki, instanceOf, building in Helsinki]
-
A.
Alvar Aalto building
An Alvar Aalto building is a modernist architectural work characterized by organic forms, human-centered design, and innovative use of natural materials and light, reflecting Aalto’s distinctive Scandinavian sensibility.
-
B.
building in Moscow
A building in Moscow is a constructed structure within the city’s urban environment, serving residential, commercial, governmental, or cultural functions and reflecting the architectural styles and historical layers of Russia’s capital.
-
C.
bridge in Helsinki
A bridge in Helsinki is a structural crossing—often combining functional Nordic engineering with minimalist design—that spans water or land to connect different parts of the city’s urban and coastal landscape.
-
D.
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.
-
E.
building in Germany
A building in Germany is a constructed structure located within German territory, designed for human use or occupancy and subject to German architectural, safety, and regulatory standards.
- 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_69f348d11a048190a65eb8384a3754ac |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:10 p.m.