Triple
T3840982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michigan Court of Appeals |
E93447
|
entity |
| Predicate | judgesElectedOrAppointed |
P11399
|
FINISHED |
| Object | elected |
—
|
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: elected | Statement: [Michigan Court of Appeals, judgesElectedOrAppointed, elected]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: judgesElectedOrAppointed Context triple: [Michigan Court of Appeals, judgesElectedOrAppointed, elected]
-
A.
judgesElected
Indicates that the judges in question attained their positions through an electoral process rather than by appointment or other means.
-
B.
judiciaryChosenBy
Indicates that the members of the judiciary are selected or appointed by a specified person, group, or institution.
-
C.
appointedOrElected
chosen
Indicates that an entity attained a position, role, or office through either an appointment process or an electoral process.
-
D.
appointingAuthorityForJudges
Indicates the entity that has the official power or responsibility to appoint judges.
-
E.
electorsAppointedBy
Indicates that one party is responsible for officially selecting or designating the electors who will act or vote on behalf of another entity.
- 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_69aed96ce578819084ab16e3439976c9 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeebb235088190b115623e54ea2ab1 |
completed | March 9, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69aee74dcecc819098285483ec721b40 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:18 p.m.