Triple
T16090130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open Helsinki – Embedding Design in Life |
E390339
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | urban development initiative |
C18701
|
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 development initiative Context triple: [Open Helsinki – Embedding Design in Life, instanceOf, urban development initiative]
-
A.
urban development
Urban development is the planned growth and improvement of cities and towns through the design, regulation, and construction of buildings, infrastructure, and public spaces to support economic, social, and environmental needs.
-
B.
urban development company
An urban development company is an organization that plans, finances, and executes projects to design, build, and revitalize city spaces, infrastructure, and real estate in alignment with economic, social, and environmental goals.
-
C.
development initiative
chosen
A development initiative is a coordinated set of actions and resources aimed at improving social, economic, or environmental conditions within a specific community, sector, or region.
-
D.
urban design project
An urban design project is a coordinated planning and design effort that shapes the physical form, public spaces, infrastructure, and land use of a specific urban area to improve its functionality, aesthetics, and livability.
-
E.
urban planning milestone
An urban planning milestone is a significant event, decision, or achievement that marks measurable progress in the development, implementation, or transformation of a city’s spatial, social, or infrastructural plans.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 10, 2026, 4:59 a.m.