Triple
T11730782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Attorneys’ Offices appellate units |
E278890
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | specialized division of United States Attorney’s Office |
C2175
|
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: specialized division of United States Attorney’s Office Context triple: [United States Attorneys’ Offices appellate units, instanceOf, specialized division of United States Attorney’s Office]
-
A.
specialized division
A specialized division is a distinct organizational unit focused on a specific function, expertise, or market segment to improve efficiency and effectiveness within a larger entity.
-
B.
specialized operations division
A specialized operations division is a focused organizational unit responsible for planning and executing complex, high-priority, or technically advanced missions that fall outside the scope of standard operational teams.
-
C.
component of the United States Department of Justice
chosen
A component of the United States Department of Justice is an organizational unit, such as a bureau, office, or division, that performs specific law enforcement, legal, or administrative functions under the authority and oversight of the Department.
-
D.
subdivision of court
A subdivision of court is a distinct organizational unit within a larger judicial system, defined by specific jurisdictional scope, case types, or geographic boundaries.
-
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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:41 p.m.