Triple
T30541405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raumplan concept |
E777289
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | spatial planning approach |
C40870
|
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: spatial planning approach Context triple: [Raumplan concept, instanceOf, spatial planning approach]
-
A.
spatial planning instrument
A spatial planning instrument is a formal tool, policy, or regulatory mechanism used by authorities to guide, control, and coordinate the use and development of land and space within a defined territory.
-
B.
local and regional planning framework
A local and regional planning framework is a structured set of policies, processes, and tools that guide coordinated land use, infrastructure, and development decisions across municipalities and regions to achieve sustainable, equitable, and efficient growth.
-
C.
urban planning practice
Urban planning practice is the professional process of analyzing, designing, and regulating the use of land and infrastructure in cities to guide sustainable, equitable, and functional urban development.
-
D.
urban planning model
chosen
An urban planning model is a conceptual or computational framework used to analyze, simulate, and guide the spatial organization, infrastructure, and development policies of cities and metropolitan regions.
-
E.
urban planning structure
An urban planning structure is a designed physical or organizational element within a city—such as streets, parks, zoning frameworks, or transit systems—that shapes how urban space is organized, used, and experienced.
- 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_69f2249d183c8190b79937c1768d2163 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:19 p.m.