Triple
T22497705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appellate Division (Cook County State's Attorney's Office) |
E556186
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | specialized appellate division |
C3497
|
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 appellate division Context triple: [Appellate Division (Cook County State's Attorney's Office), instanceOf, specialized appellate division]
-
A.
specialized division
chosen
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.
special court
A special court is a judicial body established to handle specific types of cases or issues outside the jurisdiction or procedures of ordinary courts, often with specialized rules, judges, or limited subject matter.
-
C.
specialized court registry
A specialized court registry is an administrative office within a particular type of court (e.g., family, commercial, or tax court) responsible for managing case filings, records, scheduling, and procedural documentation specific to that court’s jurisdiction.
-
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.
customary court of appeal
A customary court of appeal is a higher-level traditional judicial body that reviews and decides appeals from lower customary courts according to local customs and norms rather than formal statutory law.
- 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_69e11e5445bc8190b6a9481926db3355 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:50 p.m.