Triple
T33002783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philadelphia historic preservation ordinance |
E844416
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipal historic preservation law |
C5720
|
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: municipal historic preservation law Context triple: [Philadelphia historic preservation ordinance, instanceOf, municipal historic preservation law]
-
A.
historic preservation law
Historic preservation law is the body of legal rules and policies that protect, regulate, and manage historically significant buildings, sites, and artifacts to preserve cultural heritage for present and future generations.
-
B.
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.
-
C.
statewide historic preservation program
A statewide historic preservation program is a coordinated governmental initiative that identifies, protects, and promotes significant historic and cultural resources across an entire state through planning, regulation, incentives, and public engagement.
-
D.
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.
-
E.
municipal ordinance
chosen
A municipal ordinance is a local law or regulation enacted by a city or town government to govern conduct, land use, public safety, and other matters within its jurisdiction.
- 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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:23 a.m.