Triple
T11748191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Park County, Wyoming |
E279337
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | county of Wyoming |
C29743
|
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: county of Wyoming Context triple: [Park County, Wyoming, instanceOf, county of Wyoming]
-
A.
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.
-
B.
county of Kansas
A county of Kansas is an administrative subdivision of the state that serves as a local level of government, providing regional services, governance, and jurisdiction over a defined geographic area and its residents.
-
C.
county of Nebraska
A county of Nebraska is an administrative and political subdivision of the U.S. state of Nebraska, responsible for local governance, public services, and regional jurisdiction within its defined geographic boundaries.
-
D.
county in South Dakota
A county in South Dakota is an administrative and geographic subdivision of the state that provides local government services, law enforcement, and infrastructure management for the communities within its boundaries.
-
E.
county of Oklahoma
A county of Oklahoma is an administrative and geographic subdivision of the state of Oklahoma that serves as a local level of government, providing regional services, governance, and jurisdictional boundaries for communities within its area.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:41 p.m.