Triple
T13426737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Park Service documentation standards |
E313499
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic preservation standard |
C33000
|
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 standard Context triple: [National Park Service documentation standards, instanceOf, historic preservation standard]
-
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 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.
-
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 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.
-
E.
historic preservation grant
A historic preservation grant is a financial award provided to support the protection, restoration, and continued use of historically significant buildings, sites, or artifacts.
- 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:40 p.m.