Triple
T34883435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juvenile Matters Division |
E1006074
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | specialized branch of the Connecticut Superior Court |
C28278
|
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 branch of the Connecticut Superior Court Context triple: [Juvenile Matters Division, instanceOf, specialized branch of the Connecticut Superior Court]
-
A.
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.
-
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.
subdivision of court
chosen
A subdivision of court is a distinct organizational unit within a larger judicial system, defined by specific jurisdictional scope, case types, or geographic boundaries.
-
D.
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.
-
E.
inferior court
An inferior court is a lower-level judicial body whose decisions are subject to review, modification, or reversal by a higher appellate court within a legal system.
- 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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.