Triple
T26573828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wisconsin Circuit Court Access |
E666895
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | judicial branch information system |
C36544
|
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 information system Context triple: [Wisconsin Circuit Court Access, instanceOf, judicial branch information system]
-
A.
judicial network
A judicial network is a structured system of interconnected courts, judges, and legal institutions that interact through case decisions, precedents, and administrative relationships to shape and apply the law.
-
B.
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.
-
C.
electronic court records system
chosen
An electronic court records system is a digital platform that securely stores, manages, and provides controlled access to court case documents, filings, and related judicial information.
-
D.
judiciary
The judiciary is the branch of government responsible for interpreting laws, resolving disputes, and ensuring justice is administered fairly and in accordance with the constitution and legal principles.
-
E.
judicial training institute
A judicial training institute is an organization dedicated to educating, training, and continuously developing judges and other judicial officers in legal knowledge, skills, ethics, and court administration.
- 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_69ee9cfa21c081909e4e36e087debfc6 |
completed | April 26, 2026, 11:17 p.m. |
Created at: April 27, 2026, 1:59 a.m.