Triple
T19174828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State of Minnesota in civil litigation |
E469412
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | governmental party in civil cases |
C12445
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: governmental party in civil cases Context triple: [State of Minnesota in civil litigation, instanceOf, governmental party in civil cases]
-
A.
named party in court case
chosen
A named party in a court case is an individual or entity explicitly identified in legal proceedings as having a direct legal interest in the outcome, such as a plaintiff, defendant, petitioner, or respondent.
-
B.
judicial faction
A judicial faction is a group of judges or legal decision-makers within a court system who share similar interpretive philosophies, policy preferences, or ideological leanings that influence their collective rulings and legal strategies.
-
C.
court faction
A court faction is a group of influential individuals within a royal or imperial court who align around shared interests, loyalties, or ambitions to shape political decisions and power dynamics.
-
D.
litigation party role
A litigation party role represents the specific legal capacity or position (such as plaintiff, defendant, or intervenor) that a person or entity holds within a particular lawsuit or legal proceeding.
-
E.
governmental procedure
A governmental procedure is a formally established sequence of actions, rules, and decision-making steps that public authorities follow to create, implement, or enforce laws and policies.
- F. None of above.
Provenance (1 batch)
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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:06 p.m.