Triple
T36349029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zoning Evaluation Division |
E895143
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | zoning review division |
C23695
|
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: zoning review division Context triple: [Zoning Evaluation Division, instanceOf, zoning review division]
-
A.
land use review process
chosen
The land use review process is a formal, often multi-step procedure through which proposed developments or changes in land use are evaluated for compliance with zoning regulations, environmental standards, and community planning goals before approval or denial.
-
B.
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.
-
C.
zoning overlay district
A zoning overlay district is a special zoning area placed over an existing base zoning district that imposes additional or alternative land-use regulations to achieve specific planning or policy objectives.
-
D.
regulatory subdivision
A regulatory subdivision is a defined geographic or administrative area within a jurisdiction established for the purpose of applying, enforcing, or managing specific regulations, policies, or legal requirements.
-
E.
subdivision
A subdivision is a defined portion of a larger area or entity that has been divided into smaller, distinct parts for organizational, administrative, or functional purposes.
- 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.