Triple
T27628988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greater Riyadh master plan |
E696286
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | strategic urban plan |
C29334
|
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: strategic urban plan Context triple: [Greater Riyadh master plan, instanceOf, strategic urban plan]
-
A.
urban planning master plan
chosen
An urban planning master plan is a comprehensive, long-term framework that guides the physical, social, and economic development of a city or region through coordinated land use, infrastructure, and policy strategies.
-
B.
citywide planning initiative
A citywide planning initiative is a coordinated, long-term effort by municipal stakeholders to guide land use, infrastructure, services, and development policies across an entire city to achieve shared social, economic, and environmental goals.
-
C.
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.
-
D.
planned city
A planned city is an urban area whose layout, infrastructure, and land use are deliberately designed and constructed according to a comprehensive plan before significant settlement occurs.
-
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_69ef59092c8881908114ad184248cc46 |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 27, 2026, 2:19 p.m.