Triple
T23206863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington, D.C. street grid |
E580482
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | city plan component |
C37571
|
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: city plan component Context triple: [Washington, D.C. street grid, instanceOf, city plan component]
-
A.
town plan
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.
-
B.
urban planning structure
chosen
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.
-
C.
city planner
A city planner is a professional who designs, organizes, and regulates the use of urban space to balance social, economic, environmental, and infrastructural needs for sustainable community development.
-
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.
community plan area
A community plan area is a geographically defined section of a jurisdiction for which detailed land use, development, and infrastructure policies are established to guide local growth and community character.
- 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_69e24602ae1481908aaa6bc7ca493867 |
completed | April 17, 2026, 2:38 p.m. |
Created at: April 17, 2026, 4:07 p.m.