<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>of the Third Shared Task on Artificial Intelligence for Legal Assistance at FIRE 2021</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Vedant Parikh</string-name>
          <email>vedant.parikh.6299@gmail.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Upal Bhattacharya</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Parth Mehta</string-name>
          <email>parth.mehta126@gmail.com</email>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ayan Bandyopadhyay</string-name>
          <email>bandyopadhyay.ayan@gmail.com</email>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Paheli Bhattacharya</string-name>
          <email>paheli@cse.iitkgp.ac.in</email>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Kripabandhu Ghosh</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Saptarshi Ghosh</string-name>
          <email>saptarshi@cse.iitkgp.ac.in</email>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Arindam Palg</string-name>
          <email>arindamp@gmail.com</email>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Arnab Bhattacharyah</string-name>
          <email>arnabb@cse.iitk.ac.in</email>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Prasenjit Majumder</string-name>
          <email>prasenjit.majumdar@gmail.com</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Parmonic AI</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>TCG Crest</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>India</string-name>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Amazon</institution>
          ,
          <country country="IN">India</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Dhirubhai Ambani Institute of Information and Communication Technology</institution>
          ,
          <addr-line>Gandhinagar</addr-line>
          ,
          <country country="IN">India</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Indian Institute of Science Education and Research (IISER)</institution>
          ,
          <addr-line>Kolkata</addr-line>
          ,
          <country country="IN">India</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>Indian Institute of Technology Kharagpur</institution>
          ,
          <country country="IN">India</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The third edition of the shared task on Artificial Intelligence for Legal Assistance (AILA 2021) focused on two problems: (1) Rhetorical Role labeling for Legal Judgements and (2) Legal Document Summarization. Task 1 was a continuation from the previous year, where the objective is to assign one of the rhetorical labels - Facts of the case, Ruling by the Lower Court, Argument, Statute, Precedent, Ratio of the decision, and Ruling by the Present Court - to each sentence in a case judgement (of the Supreme Court of India). For Task 2, entire texts of Supreme Court judgements were provided and the task was to generate a summary by selecting the most important content. Task 2 was further divided into two sub-tasks: (2a) Identifying “summary-worthy” sentences in a court judgement, and (2b) Generating a summary from a given court judgement.</p>
      </abstract>
      <kwd-group>
        <kwd>Rhetorical role labeling</kwd>
        <kwd>Semantic segmentation</kwd>
        <kwd>Legal document summarization</kwd>
        <kwd>Headnote generation</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        With the recent advances in Natural Language Processing and Machine Learning there is
a renewed interest in utilizing these techniques to achieve a better understanding of legal
nEvelop-O
rOcid
Majumder)
documents. The series of AILA (Artificial Intelligence for Legal Assistance) shared tasks is
aimed at solving some of the pressing problems in this domain [
        <xref ref-type="bibr" rid="ref1 ref2 ref3">1, 2, 3</xref>
        ].
      </p>
      <p>
        AILA 2021 had two tasks. Task 1 is based on the premise that Legal case documents follow a
common thematic structure with implicit sections like ‘Facts of the Case’, ‘Issues being discussed’,
‘Arguments given by the parties’, etc. popularly termed as “rhetorical roles” [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Knowledge of
such semantic segments or roles will not only enhance the readability of the documents but also
help in downstream tasks like computing document similarity, summarization [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], etc. However
this information is generally not specified explicitly in case documents, which are usually just
very long and unstructured, lacking section and paragraph headings. AILA 2021 - Task 1 is a
continuation from the previous edition of AILA[
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] and is aimed at addressing this gap.
      </p>
      <p>A new task on Legal document Summarization was introduced this year. Indian Judiciary is
one of the largest Judicial Systems in the world, consisting of the Supreme Court of India, 25
High courts and 72 District courts, all of which produce an enormous amount of data in form of
judgements and other documents. Some of these judgements can run into hundreds of pages.
Legal practitioners generally depend on manually written summaries, also known as Headnotes,
while referring to these judgements. However creating Headnotes takes considerable human
efort and is a very slow process. There is an immediate need for automatically creating these
Headnotes. Task 2 is aimed at addressing this gap.</p>
      <p>AILA 2021 witnessed a participation of 15 teams with 9 of them submitting the working
notes. We received a total of 74 runs across all the tasks. The participating teams are distributed
across India, China, Botswana, Italy, Austria and Canada, both from academic institutions as
well as industry.</p>
      <sec id="sec-1-1">
        <title>1.1. Task 1 : Rhetorical Role Labeling for Legal Judgements</title>
        <p>A case document from the Indian judiciary is usually very long and unstructured, without
any section / paragraph headings. Therefore, knowledge of which sentence belongs to which
particular rhetorical class may enhance process of understanding the document. To this end, this
task aims to classify each sentence of the document in one of the 7 semantic segments/rhetorical
roles explained below:
• Facts: sentences that denote the chronology of events that led to filing the case
• Ruling by Lower Court : since we deal with Indian Supreme Court cases, these cases
were given a preliminary ruling by some lower courts (Tribunal, High Court etc.). These
sentences correspond to the ruling/decision given by these lower courts.
• Argument: sentences that denote the arguments of the contending parties
• Statute: relevant statute cited is the ongoing case
• Precedent: relevant precedent (prior case) cited in the ongoing case
• Ratio of the decision : sentences that denote the rationale/reasoning given by the Supreme</p>
        <p>Court for the final judgement
• Ruling by Present Court : sentences that denote the final decision given by the Supreme</p>
        <p>Court for the ongoing case</p>
      </sec>
      <sec id="sec-1-2">
        <title>1.2. Task 2 : Summarization of Legal Judgements</title>
        <p>
          In a common law system like in India, past verdicts delivered by various courts in the country
are very important. These can be used as a legal basis for arguing future cases. As such, there
is a lot of interest in analyzing the past verdicts. Number of such judgements are increasing
at an exponential rate which makes it dificult for any legal professional to analyze each case
in detail. Instead they often rely on human written summaries a.k.a. ‘Headnotes’ which
are generated by Law professionals. However, getting headnotes written manually by law
professionals is a slow and expensive process, and there is a huge interest in the legal community
to generate these summaries automatically. However, few such systems exist to date for the
Indian legal documents [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ], which pose a challenge of their own due to lack of a defined structure.
Acknowledging this gap, we include a legal document summarization task in AILA this year.
The aim is to automatically generate a shorter version of original document that represents the
most important or relevant information. The task was further divided into two sub-tasks as
described below.
        </p>
        <sec id="sec-1-2-1">
          <title>1.2.1. Task 2a : Identifying ‘summary-worthy’ sentences in a court judgement</title>
          <p>Given a judgement the task is to identify sentences which are ‘summary worthy’, i.e. which
have at least some information that should be included in the summary. Often the facts and
rationale of the judgement are given more importance compared to a precedence while creating a
Headnote. In Task 2a, we aim to replicate the behaviour. We appreciate the fact that generating /
compressing sentences is not an easy task, but a system that can at least identify the “interesting”
source sentences can still be of help to legal professionals. This task can be seen as a sentence
classification task where each sentence can be either “summary worthy” or not.</p>
        </sec>
        <sec id="sec-1-2-2">
          <title>1.2.2. Task 2b : Automatically generating a summary from a given court judgement</title>
          <p>Task 2b builds on Task 2a, and aims to generate an actual summary as opposed to just selecting
informative sentences. This can be seen as a more abstractive summarization as opposed to the
extractive nature of Task 2a. Given a court judgement, the participants have to automatically
generate a summary for it. This subtask can be seen as a continuation of Task 2a or as a separate
subtask. For instance, the summary could simply be formed by collecting and reordering
the sentences identified as important in Task 2a. On the other hand, these sentences can be
compressed/re-written, or generative models can be used to obtain summaries of an abstractive
nature.</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>2. Dataset</title>
      <p>
        For both tasks we annotate publicly available judgements delivered by the Supreme Court of
India. The details of annotations for task 1 can be found in [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] and those for task 2 in [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ].
Task 1: The training set consisted of 60 annotated documents containing approx. 11,300
sentences in total across all the documents. These consist of the combined training and test
set from AILA 2020 [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. The rhetorical labels were assigned by law experts from a reputed
law school in India. As the test set, we consider a set of 10 additional case documents (2
documents from each of the 5 law domains mentioned in [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]). These documents were then
given to a law expert for annotating every sentence with one of the rhetorical labels. There are
a total of 850 sentences in the test set. A part of this dataset is also made publicly available by [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
      </p>
      <p>
        Task 2: The training data for Task 2 consisted of 500 document-summary pairs. Each
judgement is accompanied by a summary written by a legal expert. Since regular NLP pipeline
(stemmer, tokenizers, etc) doesn’t work well with legal documents, we provide a pre-processed
and sentence tokenized version of each document and summary. For each sentence in the
judgement text we will provide a noisy label (75% accurate), which indicates whether or not
the sentence is ‘summary-worthy’. Each judgement and summary sentence are additionally
labelled with one of the seven rhetorical roles mentioned in Task 1. The ‘summary-worthy’
label as well as the rhetorical roles are assigned automatically and are noisy. Details of this
annotation is available in [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. In total, the training data contained 72,192 sentences. The test
data was of 50 document-summary pairs manually annotated with summary worthy labels.
This contained a total of 5,066 sentences.
      </p>
      <p>For Task 2, since ROUGE scores are sensitive to the length of auto generated summary, which
can vary drastically across judgements, we provide the target summary lengths beforehand.
Participants are expected to generate summaries of length as close as possible to the specified
target length.</p>
    </sec>
    <sec id="sec-3">
      <title>3. Evaluation</title>
      <p>
        For Task 1, evaluation methodology was same as that in AILA 2020 [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Standard metrics of
Recall, Precision and F1-Scores were used to rank the systems. Since there is a class imbalance
among the 7 categories / rhetorical roles, we use macro-averaging at category-level. The scores
were calculated as below:
1. Recall, Precision and F-score were computed for each category of labels across all
documents.
2. The overall scores for a run are computed by averaging the scores across all categories.
      </p>
      <p>For Task 2a, we use the standard classification metrics Precision, Recall and F1-Score. We
further also report the accuracy, which is percentage of labels predicted correctly. All these
metrics are averaged across all documents.</p>
      <p>For Task 2b, we use the standard ROUGE metrics for ranking the submissions. We specifically
use ROUGE-1, ROUGE-2 and ROUGE-4 metrics for this. As, ROUGE Scores are sensitive to
document length, for each judgement ideal length was provided.</p>
      <p>Team Name</p>
      <p>Rustic
Rustic</p>
      <p>Rustic
MiniTrue
Arguably
MiniTrue
MiniTrue
SSN_NLP
Arguably
SSN_NLP
NITS Legal
NITS Legal</p>
      <p>SSN_NLP
Legal AI 2021</p>
      <p>UB_BW</p>
      <p>UB_BW
Chandigarh Concordia
Chandigarh Concordia</p>
      <p>UB_BW
Chandigarh Concordia</p>
      <p>Legal NLP
CEN NLP
Legal NLP
Legal NLP</p>
      <p>CEN NLP
Nit Agartala</p>
    </sec>
    <sec id="sec-4">
      <title>4. Methods for Task 1: Rhetorical Role Labeling</title>
      <p>We received 26 runs from 11 teams for the task1. Table 1 compares the performance of the
various runs. Brief descriptions of the methods are as follows. Details can be found in the
working notes of the respective submissions.</p>
      <p>
        • rustic[
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]: The team from Huawei Ireland Research Centre, Dublin, Ireland was the best
performing team in terms of F-Score and Recall. They treated the task as a Sequence
Tagging problem, considering long-term label dependency between the sentences within
a document. Along with that, structural, domain-specific, generic sentence embedding
were used in diferent proportions. Bi-directional Gated Recurrent Unit (GRU) along with
a Conditional Random Field (CRF) were used for tagging. They submitted 3 runs.
1This includes the teams that did not submit a working note
• minitrue: They used state-of-the-art transformer architectures such as LegalBert, RoBerta,
and Bigbird along with a feed forward neural network for rhetorical role classification.
• arguably[
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]: This team used ERNIE, ROBERTA as sequence classifier and experimented
with pre-prossessing techniques like stop words removal, punctuations removal,
lemmatizing and stemming.
• ssn_nlp[9]: This team too experimented with RoBERTa, LaBSE and BERT for the
classification task.
• nits_legal[10]: They used Legal BERT along with MLP as a classifier. Moreover,
oversampling strategy (SMOTE) for the minority class was followed.
• legal_ai: This team used recently published architecture of MiniLM to extract features,
which were used to train multi-class SVM model.
• ub_bw[11]: This group experimented with fasttext classifier, its parameters and also with
input type, namely, Unigram, Bigram and Trigram.
• Chandigarh Concordia: They attempted freezing and un-freezing all the layers of
pretrained BERT and submitted two runs for that experiment. For the third run, they
performed Sugeno Integral ensemble technique and the prediction prior runs as the input.
• Legal_NLP[12]: This team used cased and uncased BERT model experimented with the
number of epochs, learning rate and other parameters.
• cen-nlp[13]: In this approach features are extracted from sentences using Distilroberta.
      </p>
      <p>They started experimenting with basic machine learning techniques and neural
network architecture, and zero in on ANN as the best performing model. Furthermore,
hyperparameter optimization performed by using GridSearchCV.
• nit-agartala[14]: This team used BERT and data pre-processing techniques for
classification.</p>
      <p>
        We find that the best performing method which achieved an FScore of 0.557 used BiDirectional
GRU along with CRF. The best performing team also treated the task as Sequence Tagging same
as current state of the art[
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. We observe that some variant of transformers or similar language
models were widely used by almost all the teams, sometimes combined with other classifiers
(SVM, FC etc.). Deep Learning methods that could extract deep semantic features were shown
to perform much better than traditional feature based approaches. For several teams who also
participated last year, the F1 score improved compared to the previous edition.
      </p>
    </sec>
    <sec id="sec-5">
      <title>5. Methods for Task 2: Summarization of Legal Judgements</title>
      <p>For the tasks of identifying ‘summary-worthy’ sentences in a court judgement (Task 2a), and
automatically generating a summary from a given court judgement (Task 2b), we received a
total of 11 runs from 5 participating teams2. The comparative results are in Table 2 (for Task 2a)
and Table 3 (for Task 2b). We briefly describe below the methods used by each team in each of
their runs. Details can be found in the working notes of the respective submissions.
• enigma[15]: This team treated the task as binary classification task, and used sentence
embeddings from BERT pre-trained on legal corpus as features for Task 2a. For Task 2b,
all the sentences that were classified as relevant in Task 2a were taken and concatenated
together.
• nits-legal[10]: This team used legal pre-trained BERT and used sentence embeddings
2This includes the teams that did not submit a working note
generated from it as features for all the three runs submitted and also divided the training
dataset in 5 shards. For Run 1, They trained diferent MLP models for these shards.
Average of predictions from all model were considered. For Run 2, They employed the
setup used in Run 1 to multitasking objective of Rhetorical Role labeling and Summary
worthy sentence identification. In Run 3, They used of the models that are saved for Run1
and Run2. For Task 2b all the sentences that were classified as relevant were used to
form a summary. They also experimented with diferent threshold to consider a sentence
relevant.
• neuralmind : For the Task 2a, the team experimented with classical document ranking
techniques, such TextRank and BM25. For Task 2b, Apart from classical techniques, they
used recently published Long document summarizers, namely, LED and Pegasus. They
applied these models on each document into segments of 1000 words and 500 words
respectively and evaluated using zero-shot approach.
• Chandigarh Concordia: The team treated Task2a as binary classification task, and
ifnetuned pre-trained Language Models using Fast AI and Tensorflow Libraries for
submitting runs. For Task 2b, they relied on statistical approach of TextRank and applied
to Term-Document Matrix, and Cosine-similarity Matrix, created from training data
provided.
• nit-agartala[14]: This team used BERT pre-trained on legal corpus and GCN for Task 2a.</p>
      <p>For Task 2b, all the sentences that were classified as relevant in Task 2a were taken and
concatenated together to form a summary.</p>
      <p>For Task 2a (Identifying ‘summary-worthy’ sentences) the best performing run achieves a
F1 Score of 0.59, where they used sentence embeddings from BERT pretrained on legal corpus
as features. Approaches followed in Submitted Runs, can be broadly divided into classical
approaches (e.g., TextRank, BM25) and Transformer based classifier or deep learning based
summarizers (e.g., BERT pretrained on legal corpus, Pegasus, GCN etc.).</p>
      <p>For Task 2(b) (Automatically generating a summary from a given court judgement) the
best performing run achieves a ROUGE1-F1 Score of 0.644 (from nits-legal team), where they
concatenate sentences which were relevant in Task 2a; this strategy was also followed by other
teams such as nit_agartala_nlp_team and Enigma. Most of the teams filtered out relevant
sentences using runs submitted in Task 2(a) and ordered them the way they arrive in the
source legal document to form a summary. While extractive summaries are useful, the aim of a
separate sub-task 2b was to encourage teams to attempt abstractive or generative summarization.
However, most teams directly used the output of Task 2a as summary for Task 2b.</p>
    </sec>
    <sec id="sec-6">
      <title>6. Conclusions</title>
      <p>Like the previous two editions, AILA 2021 created new benchmark datasets and several systems
for two important tasks related to legal data analytics. While we retained the task on rhetorical
role labeling of sentences in Indian legal documents, a new legal document summarization task
was introduced. For the rhetorical role labeling task we saw an improvement in performance
compared to last year, which can in part be attributed to the task itself being a continuation and
several teams from last year returning this year, and in part due to additional annotated data.</p>
      <p>For the summarization task (Task 2), we expected more abstractive summaries, which was the
key reason behind introducing a separate sub-task. However, most teams chose to concatenate
the output of Task 2a and use it as a summary. This could be attributed, at least partially, to the
small size of annotated corpus (500 documents), apart from the task itself being dificult.</p>
      <p>Another observation this year is that most teams, across all tasks and subtasks, relied on a
variant of pre-trained transformer models. This also enforces our belief that a larger training
dataset will lead to a substantial improvement in the performance. We hope to ofer these tasks
again with a larger annotated dataset in future.</p>
      <p>Acknowledgements: The track organizers thank all the participants for their interest in this
track. We also thank the FIRE 2021 organizers for their support in organizing the track. The
research is partially supported by TCG CREST through the project “Smart Legal Consultant:
AI-based Legal Analytics”.
[9] S. S. Balamurali, K. S, T. D, Simple transformers in rhetoric role labelling for legal
judgements, in: FIRE 2021 (Working Notes), 2021.
[10] D. Jain, M. D. Borah, A. Biswas, Summarization of indian legal judgement documents via
ensembling of contextual embedding based mlp models, in: FIRE 2021 (Working Notes),
2021.
[11] T. Leburu-Dingalo, E. Thuma, G. Mosweunyane, N. Motlogelwa, Rhetorical role labelling
for legal judgements using fasttext classifier, in: FIRE 2021 (Working Notes), 2021.
[12] A. Mitra, Classification on sentence embeddings for legal assistance, in: FIRE 2021
(Working Notes), 2021.
[13] D. Sudharsan, A. U, P. B, S. K P, Distilroberta based sentence embedding for rhetorical role
labelling of legal case documents, in: FIRE 2021 (Working Notes), 2021.
[14] S. Rusiya, A. Sharma, D. Debbarma, S. Debbarma, Rhetorical role labelling for legal
judgements and legal document summarization, in: FIRE 2021 (Working Notes), 2021.
[15] S. Furniturewala, R. Jain, V. Kumari, Y. Sharma, Legal text classification and summarization
using transformers and joint text features, in: FIRE 2021 (Working Notes), 2021.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>P.</given-names>
            <surname>Bhattacharya</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Ghosh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Ghosh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Pal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Mehta</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Bhattacharya</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Majumder</surname>
          </string-name>
          ,
          <article-title>Overview of the FIRE 2019 AILA track: Artificial Intelligence for Legal Assistance</article-title>
          ,
          <source>in: Proceedings of FIRE 2019 - Forum for Information Retrieval Evaluation</source>
          ,
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>P.</given-names>
            <surname>Bhattacharya</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Mehta</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Ghosh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Ghosh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Pal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Bhattacharya</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Majumder</surname>
          </string-name>
          ,
          <article-title>Overview of the FIRE 2020 AILA track: Artificial Intelligence for Legal Assistance</article-title>
          ,
          <source>in: Proceedings of FIRE 2020 - Forum for Information Retrieval Evaluation</source>
          ,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>V.</given-names>
            <surname>Parikh</surname>
          </string-name>
          , U. Bhattacharya,
          <string-name>
            <given-names>P.</given-names>
            <surname>Mehta</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Bandyopadhyay</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Bhattacharya</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Ghosh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Ghosh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Pal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Bhattacharya</surname>
          </string-name>
          , P. Majumder,
          <string-name>
            <surname>AILA</surname>
          </string-name>
          <year>2021</year>
          :
          <article-title>Shared task on artificial intelligence for legal assistance</article-title>
          , in: D.
          <string-name>
            <surname>Ganguly</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Gangopadhyay</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Mitra</surname>
          </string-name>
          , P. Majumder (Eds.), FIRE 2021:
          <article-title>Forum for Information Retrieval Evaluation, Virtual Event</article-title>
          , India,
          <source>December 13 - 17</source>
          ,
          <year>2021</year>
          , ACM,
          <year>2021</year>
          , pp.
          <fpage>12</fpage>
          -
          <lpage>15</lpage>
          . URL: https://doi.org/10.1145/3503162.3506571. doi:
          <volume>10</volume>
          .1145/3503162.3506571.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>P.</given-names>
            <surname>Bhattacharya</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Paul</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Ghosh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Ghosh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Wyner</surname>
          </string-name>
          ,
          <article-title>Identification of rhetorical roles of sentences in indian legal judgments</article-title>
          ,
          <source>in: Proc. International Conference on Legal Knowledge and Information Systems (JURIX)</source>
          ,
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>P.</given-names>
            <surname>Bhattacharya</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Poddar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Rudra</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Ghosh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Ghosh</surname>
          </string-name>
          ,
          <article-title>Incorporating domain knowledge for extractive summarization of legal case documents</article-title>
          ,
          <source>in: Proceedings of the International Conference on Artificial Intelligence and Law (ICAIL)</source>
          ,
          <year>2021</year>
          , p.
          <fpage>22</fpage>
          -
          <lpage>31</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>V.</given-names>
            <surname>Parikh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Mathur</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Mehta</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Mittal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Majumder</surname>
          </string-name>
          ,
          <article-title>Lawsum: A weakly supervised approach for indian legal document summarization</article-title>
          ,
          <source>arXiv preprint arXiv:2110.01188v3</source>
          (
          <year>2021</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>S.</given-names>
            <surname>Dutta</surname>
          </string-name>
          ,
          <article-title>Categorizing roles of legal texts via sequence tagging on domain-specific language models</article-title>
          ,
          <source>in: FIRE 2021 (Working Notes)</source>
          ,
          <year>2021</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>G. S.</given-names>
            <surname>Kohli</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Kaur</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Bedi</surname>
          </string-name>
          ,
          <article-title>Automatic detection of rhetorical role labels using ernie2.0 and roberta</article-title>
          ,
          <source>in: FIRE 2021 (Working Notes)</source>
          ,
          <year>2021</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>