Triple
T11730781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Attorneys’ Offices appellate units |
E278890
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | appellate litigation unit |
C28351
|
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: appellate litigation unit Context triple: [United States Attorneys’ Offices appellate units, instanceOf, appellate litigation unit]
-
A.
advocacy unit
An advocacy unit is an organized group or department dedicated to influencing policies, decisions, or public opinion in support of specific causes or interests.
-
B.
court section
chosen
A court section is a distinct organizational unit within a court system responsible for handling specific types of cases, administrative functions, or judicial processes.
-
C.
judicial cooperation liaison unit
A judicial cooperation liaison unit is a specialized body that facilitates communication, coordination, and mutual legal assistance between national and international judicial authorities to support cross-border investigations and prosecutions.
-
D.
judicial administrative office
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.
-
E.
federal appellate jurisdictional designation
A federal appellate jurisdictional designation identifies the specific authority and scope under which a federal appellate court may hear and decide appeals from lower courts or administrative bodies.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:41 p.m.