Triple
T17479455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Idaho Administrative Office of the Courts |
E425618
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | court administrative agency |
C8184
|
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: court administrative agency Context triple: [Idaho Administrative Office of the Courts, instanceOf, court administrative agency]
-
A.
judicial administrative office
chosen
A judicial administrative office is an organizational unit within the court system responsible for managing the non-judicial functions of the judiciary, such as case processing, records management, budgeting, staffing, and overall court operations support.
-
B.
court office
A court office is an administrative unit within a judicial system responsible for managing case records, scheduling hearings, processing legal documents, and supporting the day-to-day operations of the court.
-
C.
administrative tribunal
An administrative tribunal is a specialized quasi-judicial body that resolves disputes and makes determinations arising from the decisions or actions of government agencies under specific statutory frameworks.
-
D.
administrative law case
An administrative law case is a legal dispute that arises from actions or decisions of government agencies, focusing on the interpretation, application, or validity of administrative rules and procedures.
-
E.
branch court
A branch court is a subsidiary judicial facility or division located away from a main courthouse to provide more accessible legal services within a specific geographic area.
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:48 a.m.