Triple
T10677821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telluride Historic District |
E251664
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic site in Colorado |
C11600
|
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 site in Colorado Context triple: [Telluride Historic District, instanceOf, historic site in Colorado]
-
A.
Colorado state park
A Colorado state park is a designated natural or recreational area within the state of Colorado that is managed by Colorado Parks and Wildlife to conserve resources and provide public outdoor recreation opportunities.
-
B.
United States National Monument
A United States National Monument is a protected area designated by the federal government, typically by presidential proclamation, to preserve significant natural, cultural, historical, or scientific features.
-
C.
municipality in Colorado
A municipality in Colorado is an incorporated local government entity—such as a city or town—established under state law to provide public services, governance, and regulations within a defined geographic area in Colorado.
-
D.
Historic site
chosen
A historic site is a location of significant past events, structures, or cultural heritage that is preserved and recognized for its historical importance.
-
E.
United States National Historical Park
A United States National Historical Park is a protected area designated by the federal government to preserve and interpret places of national historical significance, often encompassing multiple sites or a large landscape associated with important events, people, or themes in American history.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:10 p.m.