Triple
T1763836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Davis County, Iowa Territory |
E38717
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | county of Iowa Territory |
C1632
|
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 Iowa Territory Context triple: [Davis County, Iowa Territory, instanceOf, county of Iowa Territory]
-
A.
county of Iowa
A county of Iowa is an administrative and political subdivision of the state of Iowa that provides local government services, governance, and jurisdiction over a defined geographic area and its residents.
-
B.
county in Iowa
chosen
A county in Iowa is an administrative subdivision of the state that provides local government services, including law enforcement, courts, property records, and infrastructure management, for the residents within its geographic boundaries.
-
C.
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.
-
D.
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.
-
E.
county of Illinois
A county of Illinois is a primary administrative and political subdivision of the state of Illinois, responsible for local governance functions such as law enforcement, courts, property assessment, and infrastructure within its defined geographic boundaries.
- 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_69a8862d562481908d7025a1c1f67c0d |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:31 p.m.