Triple
T4435781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | southeastern South Dakota |
E95645
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | region of South Dakota |
C143
|
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: region of South Dakota Context triple: [southeastern South Dakota, instanceOf, region of South Dakota]
-
A.
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.
-
B.
region of the United States
chosen
A region of the United States is a geographically or culturally defined area within the country that shares common characteristics such as climate, history, economy, or social identity.
-
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 of New Mexico
A county of New Mexico is a primary local government and administrative subdivision of the state, responsible for regional services, governance, and jurisdiction within its defined geographic boundaries.
-
E.
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.
- 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_69b3453ea2b48190a26f154b3b8fece5 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:31 p.m.