Triple
T9490075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arizona judiciary |
E228862
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | branch of state government |
C831
|
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: branch of state government Context triple: [Arizona judiciary, instanceOf, branch of state government]
-
A.
branch of government
chosen
A branch of government is a major division of a state's governing system, such as the executive, legislative, or judicial branch, each with distinct powers and responsibilities designed to balance and limit authority.
-
B.
executive branch agency
An executive branch agency is a governmental organization within the executive branch responsible for implementing, administering, and enforcing laws and public policies under the direction of the chief executive.
-
C.
system of government agencies
A system of government agencies is an organized network of public institutions, each with specific legal authority and responsibilities, that collectively implement laws, deliver services, and administer public policy on behalf of the state.
-
D.
state government office
A state government office is an administrative entity within a state’s governmental structure responsible for implementing specific public policies, services, and regulatory functions under the authority of state law.
-
E.
state government agency
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.
- 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_69ca847424f081908180305555139f7a |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 7:55 p.m.