Triple
T31735478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utah Supreme Court |
E809982
|
entity |
| Predicate | judicialSelectionSystem |
P145221
|
FINISHED |
| Object | merit-based selection |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: merit-based selection | Statement: [Utah Supreme Court, judicialSelectionSystem, merit-based selection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: judicialSelectionSystem Context triple: [Utah Supreme Court, judicialSelectionSystem, merit-based selection]
-
A.
judiciaryChosenBy
Indicates that the members of the judiciary are selected or appointed by a specified person, group, or institution.
-
B.
jurySelectionMethod
Indicates the process or criteria used to choose individuals who will serve on a jury.
-
C.
usesJudicialSelectionMethod
chosen
Indicates that a judicial body or jurisdiction employs a particular method or process for selecting judges.
-
D.
justicesSelectedFrom
Indicates that certain justices are chosen or appointed from a particular group, body, or pool of candidates.
-
E.
judiciaryProvision
Indicates the legal or constitutional rules, arrangements, or measures that establish, organize, or govern the functioning of the judiciary.
- F. None of above.
Provenance (3 batches)
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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ab22f464819098766f11b1c3c846 |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:23 p.m.