Triple
T1104619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crawford County, Kansas |
E25458
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | county of Kansas |
C7055
|
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 Kansas Context triple: [Crawford County, Kansas, instanceOf, county of Kansas]
-
A.
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.
-
B.
county of Missouri
A county of Missouri is a local governmental subdivision of the state of Missouri that provides regional administration, services, and governance for the residents within its defined geographic boundaries.
-
C.
county in Missouri
A county in Missouri is an administrative subdivision of the state that provides local government services, maintains public records, and oversees regional functions such as law enforcement, courts, and infrastructure for the communities within its boundaries.
-
D.
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.
-
E.
county of Kentucky
A county of Kentucky is a local governmental and geographic subdivision of the Commonwealth of Kentucky, responsible for regional administration, services, and jurisdiction within its defined boundaries.
- 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_69a49428d4448190b3b36991ceae87ce |
completed | March 1, 2026, 7:31 p.m. |
Created at: March 1, 2026, 7:43 p.m.