TL;DR
For classification, the graph-structured EKG-GNN obtains Micro-F1@0.5 of 0.642 on the 22-document held-out set, compared with 0.590 for raw-text LEGAL-BERT and 0.583 for linearized-EKG LEGAL-BERT. The paper reports an absolute gain of 0.052 Micro-F1, or 8.8% relative to the raw-text baseline.
Source: [19]
In the document-scoped FAQ, EKG-only retrieval achieves mean Token-F1 of 0.446, versus 0.323 for raw text and 0.363 for hybrid text plus EKG. On the 299 questions scored under all three conditions, paired tests found EKG-only higher than raw text by 0.123 F1 and higher than hybrid by 0.083; the paper reports that all three paired tests agreed in direction and significance.
In the 117-question bar-exam Experiment A, raw-document retrieval achieves 85.47% accuracy and chunked-text and EKG retrieval each achieve 86.32%, a 0.85 percentage-point gain over raw documents. No pairwise comparison is statistically significant; the authors therefore report no significant retrieval-condition difference in this experiment.
In open retrieval over 856,835 legal passages for 100 MBE-style questions, BM25 and E5 retrieve the gold passage in the top ten for 1% of questions, while hybrid Graph-RAG reaches 8% Recall@10. The gold passage is present in the BM25 top-1,000 pool for only eight questions, limiting downstream gains because graph reranking cannot recover passages absent from that candidate pool.
The authors report that the corpus comprises 153 complaints from five districts and does not establish generalization to other claims, jurisdictions, or legal genres. Several evaluations are small: 24 chunks for mini-graph quality, five documents for merger comparison, and 100–117 questions for bar-exam studies. The FAQ is document-scoped, and clustering lacks attorney relevance judgments, so neither establishes end-to-end similar-case retrieval. Human graph evaluators were four project members rather than legal practitioners, LLM judges may share system biases, and OCR, extraction, coreference, and inferred temporal or causal errors can propagate. The 82% oracle-document result changes retrieval scope, prompt, and context together and is not a graph-only ablation.
Source: [23]
Why This Matters
Source-paper contributions
The authors present ARGUS, a source-grounded, role-aware pipeline for constructing document-level Event Knowledge Graphs (EKGs) from U.S. employment-discrimination complaints, representing events with participants, temporal relations, and causal relations.
Source: [9]
Evaluation datasets
The document-scoped FAQ benchmark contains 300 questions over 10 CourtListener complaints, with 30 questions per document. Because each question is paired with its source complaint, the experiment measures representation and reasoning after the relevant document is known, not first-stage retrieval across CourtListener.
The corpus contains 153 CourtListener U.S. federal employment-discrimination complaints from five district courts. These are initiating pleadings describing allegations, not facts established by a court; accordingly, ARGUS events represent complaint allegations and should not be interpreted as adjudicated findings.
Source: [13]
Comparison baselines
The document-scoped FAQ compares raw-document retrieval, hybrid text plus EKG, and EKG-only retrieval while holding GPT-4o and the answering prompt fixed; answer quality is measured using Token-F1 against the gold answer.
The paper compares raw complaint text encoded from a 512-token input, a linearized entity/event EKG, and a graph-structured EKG using participation, temporal, and causal edges over the same classification label space.
Source: [7]
What the paper contributes
Key Findings
Paper reports
Limitations
The authors characterize ARGUS as a research prototype for retrieval and organization rather than legal advice, and state that automatically extracted roles, events, and causal relations may be incomplete or wrong and should not be treated as legal findings or used without attorney review.
Source: [22]
How the method works
ARGUS processes complaint FACTS narratives through sentence-level fact extraction, semantic chunking, two-stage mini-graph extraction, and deterministic plus LLM-assisted document-level merging; the authors evaluate components separately to distinguish errors from fact selection, event and relation extraction, and graph merging.
Source: [10]
The event representation uses entity records with canonical legal roles and event records with event type, participants, temporal information, source evidence, and confidence. It supports BEFORE, AFTER, OVERLAP, and SAME-TIME temporal relations and CAUSES, ENABLES, and PREVENTS causal relations, retaining relations only when supported by source text.
Source: [20]
In two-stage mini-graph extraction, Stage 1 extracts grounded entities and events without temporal or causal edges; Stage 2 receives the original chunk and Stage 1 output and adds only source-supported temporal and causal relations. Both stages require strict JSON, preservation of sentence identifiers, and no unsupported entities, events, dates, or relations.
Research question and scope
The paper asks whether the staged pipeline can produce reliable, source-grounded legal event graphs; whether those graphs improve legal classification and document-scoped question answering over text-based representations; and whether benefits extend to external and open-retrieval legal QA.
Training setup
For the reported graph classifier, LEGAL-BERT encodes graph-node descriptions; two mean-neighbor graph-convolution layers are followed by mean pooling and a 23-label classification head. The reported configuration jointly fine-tunes LEGAL-BERT and graph layers using weighted binary cross-entropy and AdamW.
Source: [4]
Paper Details
Machine Learning · System Artifact
Original research: ARGUS: Role-Aware Event Knowledge Graphs for U.S. Employment-Discrimination Complaints · 2609.30184v1
Paper authors: Sriram Kannan, Swetha Saseendran, Vishnu Vardhan Reddy Kandi, Leslie Barrett, Madhavan Seshadri, Enrico Santus
Source license: CC BY-SA 4.0. This article summarizes and interprets the source using AI. Attribution does not imply endorsement by the source authors.
This adapted analysis is shared under the same CC BY-SA 4.0 license. This brief was checked offline against its admitted source evidence. A model semantic verdict was not obtained because of the retained capacity boundary. It is not presented as model-certified or independently replicated.
- Canonical source identity
- arXiv 2609.30184
- Analyzed source version
- v1
- Source retrieved
- BaitaPhish analysis published
- BaitaPhish analysis reviewed
Evidence & Provenance
Show evidence locators
Evidence labels locate support in the original paper; they do not establish independent replication.
- [1] · page 3 — Source passage: Admitted source passage
- [2] · page 7 — Source passage: Admitted source passage
- [3] · page 7 — Source passage: Admitted source passage
- [4] · page 6 — Source passage: Admitted source passage
- [5] · page 8 — Source passage: Admitted source passage
- [6] · page 5 — Source passage: Admitted source passage
- [7] · page 6 — Source passage: Admitted source passage
- [8] · page 8 — Source passage: Admitted source passage
- [9] · page 2 — Source passage: Admitted source passage
- [10] · page 2 — Source passage: Admitted source passage
- [11] · page 8 — Source passage: Admitted source passage
- [12] · page 7 — Source passage: Admitted source passage
- [13] · page 4 — Source passage: Admitted source passage
- [14] · page 7 — Source passage: Admitted source passage
- [15] · page 7 — Source passage: Admitted source passage
- [16] · page 7 — Source passage: Admitted source passage
- [17] · page 7 — Source passage: Admitted source passage
- [18] · page 8 — Source passage: Admitted source passage
- [19] · page 6 — Source passage: Admitted source passage
- [20] · page 3 — Source passage: Admitted source passage
- [21] · page 8 — Source passage: Admitted source passage
- [22] · page 9 — Source passage: Admitted source passage
- [23] · page 9 — Source passage: Admitted source passage
- [24] · page 1 — Source passage: Admitted source passage
- [25] · page 6 — Source passage: Admitted source passage
- [26] · page 3 — Source passage: Admitted source passage