Triple
T23095953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Idaho Department of Administration |
E575888
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Idaho state agency |
C2542
|
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: Idaho state agency Context triple: [Idaho Department of Administration, instanceOf, Idaho state agency]
-
A.
state government agency
chosen
A state government agency is an official public organization established by a state to implement laws, deliver services, and administer specific policy areas within that state’s jurisdiction.
-
B.
municipality in Idaho
A municipality in Idaho is an incorporated local government entity, such as a city or town, that provides public services and governance within a defined geographic area of the state of Idaho.
-
C.
county in Idaho
A county in Idaho is an administrative subdivision of the state of Idaho that has its own local government and defined geographic boundaries, responsible for providing regional services such as law enforcement, courts, and infrastructure management.
-
D.
interstate agency
An interstate agency is an organization formed by two or more states through a formal agreement to collaboratively manage shared resources, services, or regulatory responsibilities across their borders.
-
E.
state regulatory agency
A state regulatory agency is a government body at the state level responsible for creating, implementing, and enforcing rules and standards within specific sectors (such as utilities, health, or finance) to protect the public interest and ensure legal compliance.
- 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_69e245c060b48190a9bd61a47a16db17 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:57 p.m.