Triple
T11967372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. federal greenbelt towns |
E284823
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | planned community program |
C3768
|
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 program Context triple: [U.S. federal greenbelt towns, instanceOf, planned community program]
-
A.
community-based program
A community-based program is an organized set of activities and services designed and delivered within a local community to address shared needs, build capacity, and improve well-being through active resident participation and local partnerships.
-
B.
community development program
chosen
A community development program is an organized initiative designed to improve the social, economic, and environmental well-being of a specific community through collaborative planning, resource mobilization, and capacity-building activities.
-
C.
planned residential community
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.
-
D.
regional planning program
A regional planning program is an organized framework of policies, strategies, and actions designed to guide the coordinated development, land use, infrastructure, and resource management of a specific geographic area over time.
-
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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:46 p.m.