Triple
T28215577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rise |
E711303
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | planned community neighborhood |
C5974
|
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 community neighborhood Context triple: [Rise, instanceOf, planned community neighborhood]
-
A.
planned residential community
chosen
A planned residential community is a deliberately designed neighborhood or development where housing, infrastructure, amenities, and land use are pre-organized to create a cohesive living environment.
-
B.
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.
-
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.
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.
-
E.
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.
- 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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
Created at: April 27, 2026, 10:42 p.m.