Triple
T23416969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nevada irrigation districts |
E560536
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | type of local governmental entity |
C15097
|
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: type of local governmental entity Context triple: [Nevada irrigation districts, instanceOf, type of local governmental entity]
-
A.
local governmental entity
chosen
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.
municipality type
A municipality type is a classification that defines the legal, administrative, or functional category of a local government unit (such as city, town, or village) within a given jurisdiction.
-
C.
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.
-
D.
administrative territorial entity
An administrative territorial entity is a geographically defined area governed by an authority that exercises administrative, political, or legal control within its boundaries.
-
E.
municipal organization
A municipal organization is a local government entity responsible for providing public services, managing community resources, and implementing policies within a city, town, or other local 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_69e2454cb1108190ab21ada5411a7146 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 5:39 p.m.