Triple
T10033028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon State Historic Preservation Office |
E204895
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state historic preservation office |
C5566
|
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: state historic preservation office Context triple: [Oregon State Historic Preservation Office, instanceOf, state historic preservation office]
-
A.
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.
-
B.
historic preservation organization
chosen
A historic preservation organization is a group dedicated to identifying, protecting, and promoting buildings, sites, and artifacts of historical, cultural, or architectural significance.
-
C.
California state historic preservation program
The California state historic preservation program is a government-led initiative that identifies, protects, and promotes the state’s historically and culturally significant buildings, sites, and landscapes through designation, regulation, and public support.
-
D.
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.
-
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_69ca834d77188190ad645e33e8ca3200 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 8:54 p.m.