Triple
T14311632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Director of the Administrative Office of the United States Courts |
E354846
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal judicial branch position |
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: federal judicial branch position Context triple: [Director of the Administrative Office of the United States Courts, instanceOf, federal judicial branch position]
-
A.
judicial office
A judicial office is an official position within the judiciary in which an individual is authorized to interpret and apply the law, preside over legal proceedings, and issue binding decisions.
-
B.
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.
-
C.
federal court
A federal court is a judicial body established by a national government with authority to hear and decide cases arising under that nation’s constitution, federal laws, and treaties.
-
D.
Judicial body
A judicial body is an official group or institution empowered by law to interpret and apply legal rules, resolve disputes, and administer justice.
-
E.
United States federal government position
A United States federal government position is an official role within the executive, legislative, or judicial branches of the federal government, established by law or regulation to perform specific public duties and functions on behalf of the nation.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:12 a.m.