Triple
T21484163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missouri Nonpartisan Court Plan |
E530072
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | judicial selection system |
C27192
|
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 selection system Context triple: [Missouri Nonpartisan Court Plan, instanceOf, judicial selection system]
-
A.
judicial appointments body
chosen
A judicial appointments body is an institution or committee responsible for selecting, recommending, or approving candidates for judicial office, often to promote independence, merit, and transparency in the judiciary.
-
B.
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.
-
C.
committee system
A committee system is an organizational structure in which decision-making and oversight responsibilities are delegated to specialized groups of members who meet, deliberate, and make recommendations or binding decisions within defined areas of authority.
-
D.
judicial discipline system
A judicial discipline system is a formal framework of rules, procedures, and oversight mechanisms designed to investigate, evaluate, and sanction misconduct or ethical violations by judges to maintain integrity and public confidence in the judiciary.
-
E.
judicial office
A judicial office is an official position within the judiciary in which an individual is authorized to interpret and apply the law, preside over legal proceedings, and issue binding decisions.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:21 p.m.