Triple
T34497997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 37th Judicial Circuit Court of Michigan |
E885663
|
entity |
| Predicate | hasElectedJudges |
P48882
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [37th Judicial Circuit Court of Michigan, hasElectedJudges, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElectedJudges Context triple: [37th Judicial Circuit Court of Michigan, hasElectedJudges, true]
-
A.
hasJudges
Indicates that one entity serves as a judge or panel of judges for another entity, such as an event, competition, or legal case.
-
B.
judgesElected
chosen
Indicates that the judges in question attained their positions through an electoral process rather than by appointment or other means.
-
C.
hasJudgesAppointedBy
Indicates that one entity serves as a judge who has been formally appointed by another entity.
-
D.
hasJudge
Indicates that a legal case, proceeding, or decision is presided over or decided by a particular judge.
-
E.
hasJudgeFrom
Indicates that an entity has a judge whose origin, affiliation, or source is from a specified place or organization.
- 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_69f349cafcec8190997b45b3fdc16c27 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 1, 2026, 2:01 a.m.