Triple
T16267319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michigan Court of Claims |
E394906
|
entity |
| Predicate | currentJudgesAre |
P50731
|
FINISHED |
| Object | judges of the Michigan Court of Appeals |
—
|
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: judges of the Michigan Court of Appeals | Statement: [Michigan Court of Claims, currentJudgesAre, judges of the Michigan Court of Appeals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentJudgesAre Context triple: [Michigan Court of Claims, currentJudgesAre, judges of the Michigan Court of Appeals]
-
A.
judgesAre
Indicates that one entity serves as a judge or evaluator of another entity.
-
B.
hasJudges
Indicates that one entity serves as a judge or panel of judges for another entity, such as an event, competition, or legal case.
-
C.
judgesElected
Indicates that the judges in question attained their positions through an electoral process rather than by appointment or other means.
-
D.
judgesMayBe
Indicates that certain individuals can serve in the role of judges under specified conditions or classifications.
-
E.
statusInJudges
chosen
Indicates that an entity holds a particular role, position, or standing within a group or body of judges.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c963ec8190b059fecac6248cd9 |
completed | April 17, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:05 a.m.