Triple
T9671282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glasgow city centre grid |
E234033
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | planned urban layout |
C15908
|
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: planned urban layout Context triple: [Glasgow city centre grid, instanceOf, planned urban layout]
-
A.
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.
-
B.
town plan
chosen
A town plan is a comprehensive design that organizes the spatial layout, land use, infrastructure, and public spaces of a town to guide its development and functioning.
-
C.
planned garden city
A planned garden city is a deliberately designed urban settlement that integrates residential, commercial, and green spaces in a balanced layout to promote healthy living, social cohesion, and environmental sustainability.
-
D.
planned commercial district
A planned commercial district is a deliberately designed area designated for concentrated business, retail, and service activities, typically guided by zoning regulations and urban planning principles to support economic activity and accessibility.
-
E.
historic urban layout
A historic urban layout is the enduring spatial arrangement of streets, plots, public spaces, and building patterns that reflects the social, economic, and cultural organization of a city in a past period.
- 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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:15 p.m.