Triple
T10044110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Van Buren County, Missouri |
E205368
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former county of Missouri |
C27340
|
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: former county of Missouri Context triple: [Van Buren County, Missouri, instanceOf, former county of Missouri]
-
A.
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.
-
B.
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.
-
C.
municipality in Missouri
A municipality in Missouri is an incorporated local government entity within the state of Missouri, such as a city, town, or village, that has legal authority to provide services and enact ordinances for its residents.
-
D.
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.
-
E.
county in Arkansas
A county in Arkansas is an administrative and geographic subdivision of the state of Arkansas that serves as a local level of government, providing services such as law enforcement, courts, and public records for its residents.
- 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_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 8:55 p.m.