Triple
T13786308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empowerment Zones and Enterprise Communities program |
E331266
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | place-based policy initiative |
C21902
|
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: place-based policy initiative Context triple: [Empowerment Zones and Enterprise Communities program, instanceOf, place-based policy initiative]
-
A.
local and regional planning framework
A local and regional planning framework is a structured set of policies, processes, and tools that guide coordinated land use, infrastructure, and development decisions across municipalities and regions to achieve sustainable, equitable, and efficient growth.
-
B.
town planning policy
Town planning policy is a set of rules and guidelines that shape how land is used and developed in a town to balance social, economic, and environmental needs.
-
C.
statewide initiative
chosen
A statewide initiative is a coordinated program or campaign implemented across an entire state to address a specific policy, social, economic, or public service goal.
-
D.
zoning initiative
A zoning initiative is a coordinated effort, typically led by local government or community stakeholders, to create, revise, or implement land-use regulations that guide how property within a jurisdiction can be developed and used.
-
E.
policy development community
A policy development community is a collaborative group of stakeholders who collectively research, debate, draft, and refine policies to address shared issues or goals.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:11 p.m.