Triple
T29697659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helsinki seaside recreation areas |
E751395
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | urban coastal green infrastructure |
C26361
|
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: urban coastal green infrastructure Context triple: [Helsinki seaside recreation areas, instanceOf, urban coastal green infrastructure]
-
A.
urban environmental complex
An urban environmental complex is an integrated system of natural and built elements within a city—such as green spaces, water bodies, infrastructure, and human activities—that interact to shape the urban ecosystem’s ecological, social, and climatic conditions.
-
B.
urban environmental project
An urban environmental project is an organized initiative aimed at improving the ecological health, sustainability, and livability of city spaces through interventions such as green infrastructure, pollution reduction, and community engagement.
-
C.
urban bushland
Urban bushland is a natural or semi-natural area of native vegetation within or adjacent to a city, providing habitat for wildlife and ecological services amid the built environment.
-
D.
urban public space
An urban public space is a publicly accessible area within a city—such as streets, parks, plazas, and squares—designed or used for social interaction, movement, recreation, and civic life.
-
E.
waterfront public space
chosen
A waterfront public space is a shared, accessible area along a body of water designed for recreation, social interaction, and enjoyment of the natural and urban waterfront environment.
- 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_69f0d6266f8481909e70bb41cda18587 |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 7:21 p.m.