Triple
T784321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LaRue County, Kentucky |
E16567
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | county in Kentucky |
C3947
|
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 in Kentucky Context triple: [LaRue County, Kentucky, instanceOf, county in Kentucky]
-
A.
county of Kentucky
chosen
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.
-
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.
county of West Virginia
A county of West Virginia is a primary administrative and political subdivision of the U.S. state of West Virginia, responsible for local governance, public services, and regional administration within its defined geographic boundaries.
-
D.
county in Virginia
A county in Virginia is a primary local government and geographic subdivision of the Commonwealth of Virginia, responsible for providing regional services, administration, and governance to the communities within its boundaries.
-
E.
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.
- 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_69a4936ad1fc81908f190208059ccf78 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:37 p.m.