Triple
T20789245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LaRue County courts |
E511726
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local government judicial body |
C32256
|
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: local government judicial body Context triple: [LaRue County courts, instanceOf, local government judicial body]
-
A.
local governmental entity
A local governmental entity is an administrative organization, such as a city, county, or district, that exercises governmental authority and provides public services within a specific geographic area below the level of the central or national government.
-
B.
system of local government
A system of local government is an organized framework of institutions, powers, and processes through which local authorities manage public services, enforce regulations, and represent community interests within a defined geographic area.
-
C.
local justice system
chosen
The local justice system is the network of community-level institutions, processes, and actors responsible for enforcing laws, resolving disputes, and administering justice within a specific geographic area.
-
D.
county-level jurisdiction
A county-level jurisdiction is an administrative division within a state or country that governs a specific geographic area, providing local services, regulations, and governance below the state or provincial level.
-
E.
county government
A county government is a local administrative body responsible for providing regional services, enforcing laws, managing public resources, and implementing policies within a defined county jurisdiction.
- 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_69e0b4cb83948190bd57bec21d78ed53 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:38 p.m.