Triple
T23636937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klondike National Historic Sites |
E583773
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | protected heritage area |
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: protected heritage area Context triple: [Klondike National Historic Sites, instanceOf, protected heritage area]
-
A.
Conservation area
A conservation area is a designated geographic region managed to protect and preserve its natural, cultural, or historical resources and biodiversity from degradation or unsustainable use.
-
B.
State Heritage Area
A State Heritage Area is a geographically defined place recognized and protected by a state government for its outstanding cultural, historical, or natural significance.
-
C.
protected landscape area
A protected landscape area is a designated region where the interaction of people and nature over time has produced a distinct character with significant ecological, cultural, and scenic value that is conserved and managed through legal or other effective means.
-
D.
National Heritage Area
A National Heritage Area is a region designated by the U.S. Congress where natural, cultural, and historic resources form a cohesive, nationally important landscape managed through partnerships rather than federal land ownership.
-
E.
historical district
A historical district is a geographically defined area recognized for its concentration of buildings, structures, and sites that collectively reflect significant cultural, architectural, or historical heritage.
- 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_69e248fe1c2c8190ac914d2442ff3d26 |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:47 p.m.