Figurative Justice: Detecting metaphors in Hindi judgements with qualitative assessment and transformers

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

arXiv:2608.22446v1 Announce Type: new Abstract: Metaphors are figurative use of words for conceptual mapping. Metaphor detection in the legal context has been crucial as metaphors are persuasive juridical means of creating legal meaning and concepts resulting in significant consequences. Metaphorical framing in legal discourse by judges, lawyers, and legislators brings about real-time implications upon individuals and influences judicial decision-making, argumentation and interpretation of laws. This is crucial in Human Rights infringement cases where language determines severity of punishment, public perception and judicial outcomes. While automatic metaphor detection in major languages like English, Spanish, Polish, Lithuanian have aided in understanding inherent intentions of metaphorical use of language, there is no such attempt in low-resource languages like Hindi. The dearth of annotated legal corpora in Hindi makes it difficult to develop NLP models and detect metaphors in judicial proceedings. In the Indian context, Convolutional Neural Networks (CNNs) have been used for classification of bail judgements, however there are no existing models designed for metaphor detection. We present a Hindi Legal Metaphor Corpus (HiLeMe) by isolating judgements from Hindi Legal Data Corpus (HLDC). Legal experts annotated HiLeMe to classify metaphorical constructions using the MIPVU schema. We downstreamed an mBERT on Hindi legal metaphor detection task. We built a transformer-based architecture for metaphor detection that are known to outperform traditional models in legal …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://arxiv.org/abs/2608.22446
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.