Triple
T27335200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colorado Revised Statutes Title 33 |
E689923
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Colorado state law |
C4528
|
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: Colorado state law Context triple: [Colorado Revised Statutes Title 33, instanceOf, Colorado state law]
-
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 state law
chosen
United States state law is the body of legal rules, regulations, and judicial decisions enacted and applied by an individual U.S. state to govern conduct, resolve disputes, and organize governmental powers within its jurisdiction.
-
C.
county of Colorado
A county of Colorado is an administrative subdivision of the state that serves as a local level of government, providing regional services, governance, and jurisdictional organization for its communities and unincorporated areas.
-
D.
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.
-
E.
Oregon state court
An Oregon state court is a judicial body within the Oregon state court system that interprets and applies Oregon law to resolve civil, criminal, and administrative disputes arising under state jurisdiction.
- 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_69ef355e5b388190a8fc1eba9b4a6656 |
completed | April 27, 2026, 10:07 a.m. |
Created at: April 27, 2026, 11:40 a.m.