Triple
T35940223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highland Park-Garvanza Historic Preservation Overlay Zone |
E1039421
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic preservation overlay zone |
C47898
|
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: historic preservation overlay zone Context triple: [Highland Park-Garvanza Historic Preservation Overlay Zone, instanceOf, historic preservation overlay zone]
-
A.
historic district protection program
A historic district protection program is a coordinated set of policies, regulations, and incentives designed to preserve, maintain, and enhance the architectural, cultural, and historical character of designated areas.
-
B.
protected heritage area
chosen
A protected heritage area is a designated geographic space preserved and managed to safeguard its cultural, historical, or natural significance for present and future generations.
-
C.
historic district contributing property
A historic district contributing property is a building, structure, site, or object within a designated historic district that adds to the district’s historical, architectural, or cultural significance.
-
D.
historic district feature
A historic district feature is a physical element, structure, or landscape component within a designated historic area that contributes to its historical, architectural, or cultural significance.
-
E.
historic preservation commission
A historic preservation commission is a governing body that identifies, protects, and regulates historically significant buildings, sites, and districts within a community.
- 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_69f76e24bbd0819096b837d35371639a |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.