Sign inGet started
Paper · arXiv

Stop Removing Stopwords: How an Inherited Preprocessing Default Distorts Legal Text-as-Data

Empirical legal scholarship increasingly treats judicial text as data, and much of it still runs on sparse, interpretable pipelines (TF-IDF features and linear classifiers) because the textual feature is often the object of study rather than a means to a prediction. Yet these pipelines inherit preprocessing defaults from mid-century information retrieval that were never validated against classification accuracy. The most entrenched of these is stopword removal. This study introduces an exhaustive single-word ablation that measures a preprocessing step's effect directly against the downstream objective, and applies it to stopword removal. Matching Supreme Court Database labels to Caselaw A...

AuthorsGregory M. Dickinson
Primary categorycs.CL
Published21 July 2026
Last updated at source4 October 2026
cs.CLcs.CYcs.IRcs.LG
Embed this entry
<iframe src="https://silytics.si/embed/item/89a93fd1-88ec-4265-8e8e-40eed32ec957" width="420" height="190" style="border:0" loading="lazy" title="Silytics entry"></iframe>

Free, no tracking. More about feeds and embeds.

Silytics shows public metadata from arXiv and links to the original. Information may be incomplete or out of date. Last refreshed 17 October 2026. Licenses and terms of the original apply to the work itself. Not financial, legal or professional advice.