Triple
T32861249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridge of Lions area planning antecedents in St. Augustine |
E840522
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | urban planning study |
C60887
|
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: urban planning study Context triple: [Bridge of Lions area planning antecedents in St. Augustine, instanceOf, urban planning study]
-
A.
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.
-
B.
urban planning theory
Urban planning theory is the body of ideas, principles, and frameworks that explain how cities develop, how space is organized, and how planning decisions shape social, economic, and environmental outcomes.
-
C.
urban planning model
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.
-
D.
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.
-
E.
urban planning book
An urban planning book is a comprehensive text that explores the theories, methods, policies, and case studies involved in designing and managing the physical, social, and economic development of cities and urban regions.
- F. None of above. chosen
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_69f34942465c819099b3fb47f9044f58 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:17 a.m.