Triple
T12965960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raleigh Historic Overlay District |
E321263
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | zoning overlay district |
C32260
|
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 overlay district Context triple: [Raleigh Historic Overlay District, instanceOf, zoning overlay district]
-
A.
special-purpose district
A special-purpose district is a limited-purpose local government entity created to perform a specific public function or set of functions—such as water supply, transportation, or education—within a defined geographic area.
-
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.
metropolitan district
A metropolitan district is an administrative or governmental region that encompasses a central city and its surrounding urban and suburban areas, managed as a single integrated unit for planning, services, and governance.
-
D.
planning district
A planning district is a defined geographic area used by governments or organizations to coordinate land use, infrastructure, and development policies.
-
E.
architectural district
An architectural district is a geographically defined area characterized by a concentration of buildings and structures that share significant architectural styles, historical periods, or design features, often protected or managed for their cultural and aesthetic value.
- 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_69d80763bd6c819094437da5b20b01d2 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 8:28 p.m.