Triple
T13983584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Macadam urban renewal area |
E336376
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | redevelopment district |
C5822
|
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: redevelopment district Context triple: [North Macadam urban renewal area, instanceOf, redevelopment district]
-
A.
urban regeneration area
chosen
An urban regeneration area is a designated part of a city targeted for coordinated physical, economic, social, and environmental improvements to reverse decline and promote sustainable development.
-
B.
mixed-use development district
A mixed-use development district is a designated urban area that intentionally combines residential, commercial, recreational, and sometimes industrial uses within a walkable, integrated environment to promote vibrant, efficient, and sustainable community life.
-
C.
planning district
A planning district is a defined geographic area used by governments or organizations to coordinate land use, infrastructure, and development policies.
-
D.
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.
-
E.
reconstructed historic district
A reconstructed historic district is an area where buildings, streetscapes, and public spaces have been rebuilt or extensively restored to replicate their historical appearance and character, often based on archival research and archaeological evidence.
- 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_69d81c639e808190a0e4b4f3d31c6a59 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:18 p.m.