Triple
T16090131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open Helsinki – Embedding Design in Life |
E390339
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public sector design 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: public sector design initiative Context triple: [Open Helsinki – Embedding Design in Life, instanceOf, public sector design initiative]
-
A.
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.
-
B.
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.
-
C.
public-sector collaboration
Public-sector collaboration is the coordinated effort among government agencies and public institutions, often with private and nonprofit partners, to jointly design, implement, and manage policies or services that address shared societal challenges.
-
D.
public sector enterprise
A public sector enterprise is an organization owned and operated by the government to provide goods or services, often with broader social or strategic objectives beyond profit.
-
E.
public sector estate
A public sector estate is the collective portfolio of land, buildings, and infrastructure owned, leased, or managed by government or public bodies to deliver public services and support policy objectives.
- 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.