Triple
T16267328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michigan Court of Claims |
E394906
|
entity |
| Predicate | typeOfPartyInCases |
P26870
|
FINISHED |
| Object | plaintiffs suing the State of Michigan |
—
|
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: plaintiffs suing the State of Michigan | Statement: [Michigan Court of Claims, typeOfPartyInCases, plaintiffs suing the State of Michigan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfPartyInCases Context triple: [Michigan Court of Claims, typeOfPartyInCases, plaintiffs suing the State of Michigan]
-
A.
partyTypeOfRespondent
Indicates the specific legal or procedural role that the respondent plays as a party in a case or proceeding.
-
B.
partyTypePlaintiffs
chosen
Indicates the classification or category of the parties serving as plaintiffs in a legal action.
-
C.
partyCategory
Indicates the classification or type assigned to a party within a given context or system.
-
D.
typeOfProceedings
Indicates the specific category or kind of legal or formal process under which an action or case is being conducted.
-
E.
caseTypes
Indicates the types or categories of cases associated with or applicable to an entity or situation.
- 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.