Triple
T28225296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambridge neighborhood system |
E711569
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | urban neighborhood classification system |
C54549
|
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 neighborhood classification system Context triple: [Cambridge neighborhood system, instanceOf, urban neighborhood classification system]
-
A.
urban system
An urban system is an interconnected network of cities and their surrounding regions, encompassing the flows of people, goods, information, and resources that shape their social, economic, and environmental dynamics.
-
B.
urban block
An urban block is a contiguous group of buildings and parcels of land bounded by streets or public spaces, forming a basic unit of urban fabric and development.
-
C.
neighborhood
A neighborhood is a geographically localized community within a larger city or town, characterized by shared residential spaces, social interactions, and common amenities.
-
D.
urban design recognition
Urban design recognition is the process of identifying, interpreting, and classifying the spatial, visual, and functional patterns of built environments within cities.
-
E.
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.
- 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_69efb51dfb048190ada79b745c33b363 |
completed | April 27, 2026, 7:12 p.m. |
Created at: April 27, 2026, 10:49 p.m.