Triple
T15270525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States District Court Clerk’s Office |
E365008
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | judicial branch administrative unit |
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: judicial branch administrative unit Context triple: [United States District Court Clerk’s Office, instanceOf, judicial branch administrative unit]
-
A.
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.
-
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.
judicial branch employees
Judicial branch employees are individuals who work within the court system to support the administration of justice, including judges, clerks, court reporters, and other legal and administrative staff.
-
D.
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.
-
E.
high court branch
A high court branch is a regional division or bench of a higher judiciary that exercises the court’s jurisdiction over a specific geographic area, hearing appeals and significant legal matters within that territory.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:14 a.m.