Triple
T1113685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York City Landmarks Law |
E11048
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipal preservation statute |
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 preservation statute Context triple: [New York City Landmarks Law, instanceOf, municipal preservation statute]
-
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.
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.
-
C.
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.
-
D.
historic preservation subject
A historic preservation subject is any building, site, structure, object, or district recognized for its historical, architectural, cultural, or archaeological significance and considered for protection, conservation, or restoration.
-
E.
historic preservation project
A historic preservation project is a coordinated effort to identify, protect, restore, and maintain buildings, sites, or artifacts of historical, cultural, or architectural significance for present and future generations.
- 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_69a493252a648190ac48f8742474a5e8 |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:43 p.m.