MétaCan
Menu
Back to cohort
Record W2886473766 · doi:10.1111/jels.12186

A Rose by Any Other Name: Understanding Judicial Decisions that Do Not Cite Precedent

2018· article· en· W2886473766 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueJournal of Empirical Legal Studies · 2018
Typearticle
Languageen
FieldSocial Sciences
TopicJudicial and Constitutional Studies
Canadian institutionsUniversity of Toronto
Fundersnot available
KeywordsCITESSupreme courtLawPolitical scienceJudicial opinionFoundation (evidence)PhenomenonPhilosophy

Abstract

fetched live from OpenAlex

In common‐law countries, legal precedent serves as a foundation of judicial opinions. Judges cite precedent to explain their decision, and it is this use of precedent that threads one decision to another. The Supreme Court in India stands in contrast to its counterparts in other countries in that it annually decides not dozens, but thousands, of cases. Perhaps unsurprisingly, nearly half the Court's decisions do not cite any precedent at all. This article examines this phenomenon, specifically how it affects judges’ commitment to the common law, in substance if not in form. Examining every Court decision for the period 1950–2010, we textually analyze the opinions using machine learning to determine what connection, if any, exists between cases. We find that it is possible to accurately model how the Court cites to existing precedent and that even for decisions without any citations, there is almost always at least one prior decision the Court could have cited. Our finding suggest that time and resource demands are primarily responsible for the failure to cite relevant precedent, but that the Court acts efficiently, given the constraints placed on it, in deciding in which decisions to include precedent. This research, however, leaves unanswered whether the Court provides sufficient guidance to lower courts.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.002
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScience and technology studies
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.392
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.002
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.000
Science and technology studies0.0020.002
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.246
GPT teacher head0.436
Teacher spread0.190 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it