Triple
T7929566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Budget and Finance Division |
E184153
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | division of the Oregon Judicial Department |
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: division of the Oregon Judicial Department Context triple: [Budget and Finance Division, instanceOf, division of the Oregon Judicial Department]
-
A.
judicial district
A judicial district is a defined geographic area within which a particular court or set of courts has legal authority to hear and decide cases.
-
B.
division of the Judiciary of Guam
The division of the Judiciary of Guam is an organizational unit within Guam’s judicial branch responsible for carrying out specific court functions, services, or jurisdictions under the overall authority of the territory’s unified court system.
-
C.
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.
-
D.
county of Oregon
A county of Oregon is a regional administrative division of the U.S. state of Oregon that provides local government services, governance, and jurisdiction over a defined geographic area and its residents.
-
E.
subdivision of the Supreme Court of Japan
A subdivision of the Supreme Court of Japan is an internal organizational unit, such as a petty bench or administrative division, that handles specific categories of judicial or administrative functions within the Court.
- 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_69ca828fe7bc819090f52c88dcd72183 |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 5:07 p.m.