<!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>IITP at AILA 2019: System Report for Arti cial Intelligence for Legal Assistance Shared Task</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Baban Gain</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Dibyanayan Bandyopadhyay</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Arkadipta De</string-name>
          <email>de.arkadipta05g@gmail.com1</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Tanik Saikh</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Asif Ekbal</string-name>
          <email>asif.ekbalg@gmail.com2</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Government College Of Engineering And Textile Technology</institution>
          ,
          <addr-line>Berhampore</addr-line>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Indian Institute of Technology Patna</institution>
        </aff>
      </contrib-group>
      <abstract>
        <p>In this article, we present a description of our systems as a part of our participation in the shared task namely Arti cial Intelligence for Legal Assistance (AILA 2019). This is an integral event of Forum for Information Retrieval Evaluation - 2019. The outcomes of this track would be helpful for the automation of the working process of the Indian Judiciary System. The manual working procedures and documentation at any level (from lower to higher court) of the judiciary system are very complex in nature. The systems produced as a part of this track would assist the law practitioners'. It would be helpful for common men too. This kind of track also opens the path of research of Natural Language Processing (NLP) in the judicial domain. This track de ned two problems such as Task 1 : Identifying relevant prior cases for a given situation and Task 2 : Identifying the most relevant statutes for a given situation. We tackled both of them. Our proposed approaches are based on BM25 and Doc2Vec. As per the results declared by the task organizers', we are in 3rd and a modest position in Task 1 and Task 2 respectively.</p>
      </abstract>
      <kwd-group>
        <kwd>BM25 Doc2Vec Similarity Metrics</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        The working procedure of any judiciary system over the world is very complex
in nature. 3 The countries like India are having two primary sources of law
namely: Statutes (established laws) and Precedents (prior cases). Statutes are
applied legal principles to a situation like facts/scenario/circumstances which
lead to ling the case. Whereas, the precedents/prior cases help a lawyer to
understand how the court has dealt with similar scenarios in the past, and make
the reasoning accordingly. These kinds of tasks are very cumbersome and hard
to do manually. Automated solutions to these problems would be bene cial to
the lawyers. The system will do the task of nding relevant prior cases given
3 Copyright 2019 for this paper by its authors. Use permitted under Creative
Commons License Attribution 4.0 International (CC BY 4.0). FIRE 2019, 12-15
December 2019, Kolkata, India.
a current case and statutes/acts that will be more suited to a given situation.
These kinds of systems will be helpful to common men too. It will be able to
provide a preliminary understanding to common men on a particular case even
before going to the lawyers. It shall assist human beings in identifying where
his/her legal problem ts, what legal actions he/she can proceed with (through
statutes), and what were the outcomes of similar cases (through precedents).
The Arti cial Intelligence for Legal Assistance (AILA 2019) [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], an associated
event of Forum for Information Retrieval Evaluation 2019 has come up with two
problems viz. i. Task 1 : Identifying relevant prior cases for a given situation
and ii. Task 2 : Identifying the most relevant statutes for a given situation. The
automated solutions to these problems will mitigate such problems of lawyers as
well as common men. We took part in both the tasks de ned. We make use of
the datasets released for these tasks for our experiments. The dataset is having a
set of 50 queries, each of which contains the description of a situation. In Task1,
almost 3000 case documents of cases that were judged in the Supreme Court of
India are given. The participants of this task have to retrieve the most similar/
relevant case documents with respect to the situation in the given query. The
dataset for the Task 2 is having 197 statutes (Sections of Acts) from Indian
law, that are relevant to some of the queries. The title and the description of
these statutes are given. Task 2 is to identify the most relevant statutes (from
among the 197 statutes) for each query. These tasks could be tackled either in
supervised or unsupervised way. We make use of unsupervised approaches as the
datasets are having very less number of annotated examples.
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>Related Work</title>
      <p>
        Earlier this type of work was introduced by [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. They de ned two tasks namely i.
Catch Phrase Extraction and ii. Precedence Retrieval. This track received a lot
of responses. Another task namely Competition on Legal Information Extraction
and Entailment (COLIEE-2019), as an associated event of International
Conference on Arti cial Intelligence and Law (ICAIL)-2019 was performed in the
same line. In this competition, four tasks were de ned. Task 1 was to retrieve
the supporting cases for a new case from the whole case law corpus. Task 2 was
about to identify paragraphs from prior cases that entails the decision of a new
case. Task 3 was a legal question answering task. Task 4 was to retrieve relevant
documents given a question and then have to determine whether the relevant
articles entail the question or not. The work of [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] tackled all the problems. They
made use of BERT, BM25 and Doc2Vec models for these problems.
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>Proposed Methods and Experimentation</title>
      <p>
        We participated in both the tasks de ned. The rst task is to identify relevant
prior cases for a given situation and the other one is identifying the most relevant
statutes for a given situation. They provided datasets for both the tasks. The
dataset contains 50 queries. The queries are a description of legal situations. For
Task 1, there are 2,914 prior case documents and for Task 2, 197 statutes are
there which are basically the title and the corresponding textual description of
the statutes. We foster BM25 [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] and Doc2Vec [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] approaches for the Task 1.
Only BM25 has been used for Task 2.
3.1
      </p>
      <sec id="sec-3-1">
        <title>Task 1</title>
        <p>In this part, we discuss the preprocessing of the datasets for this task followed
by the description of the proposed approaches and experimental procedures.
Preprocessing: We perform a few preprocessing rst. For every query and
candidate document, we extract all the words. Then, remove all the numbers, that
are used to indicate paragraph number. We also remove the stop words from the
documents by using NLTK English stop words list. Then we perform stemming
and lemmatization of the words using Porter Stemmer and WordNet
Lemmatizer respectively.</p>
        <p>
          BM25: BM25 is a bag-of-words based retrieval function that ranks a set of
documents based on the query terms appearing in each document, regardless of the
inter-relationship between the query terms within a document. The objective of
the task is to retrieve the most similar/relevant case documents concerning the
situation of a given query document. The dataset contains 2914 candidates and
50 queries, among which 10 queries are used as train cases and 40 queries are
used for the testing purpose as directed by the task organizers'.
Doc2Vec: Doc2Vec is an unsupervised algorithm that learns xed-length
feature representations from variable-length pieces of texts, such as sentences,
paragraphs, and documents. This algorithm represents each document by a dense
vector that is trained to predict words in the document. More precisely, we
concatenate the paragraph vector with several word vectors from a paragraph and
predict the following word for the given context. Both word vectors and
paragraph vectors are trained by the stochastic gradient descent and backpropagation
[
          <xref ref-type="bibr" rid="ref6">6</xref>
          ]. While paragraph vectors are unique among paragraphs, the word vectors are
shared. At prediction time, the paragraph vectors are inferred by xing the word
vectors and training the new paragraph vector until convergence.
We submitted two runs for the task:
{ IIT P BM 25 case: We compute the BM25 similarity score (as mentioned
earlier) for a query document with every candidate cases, and then the
candidates are returned as in decreasing order of the similarity score between a
query document and a candidate case.
{ IIT P Doc2V ec case: We train a gensim Doc2Vec model using candidate
cases and query documents. The hyperparameters applied are as follows:
Vector dimension: 150, window: 20, epoch: 50. After training, we get
document vectors for every query and candidate document. Then we calculate
the Doc2Vec similarity score between the query document and every
candidate document. Then the candidates are returned in decreasing order of
similarity score with the query.
        </p>
      </sec>
      <sec id="sec-3-2">
        <title>Task 2</title>
        <p>The objective of this task is to identify the most relevant statues for a given
query document. The dataset consisting of 197 statutes and 50 queries among
which 10 queries are used for training purpose and 40 queries for testing purpose.
Preprocessing: For every query and statute, we extract all the words. We
perform removal of stop words, stemming and lemmatization of words using NLTK
English stop words list, Porter Stemmer and WordNet Lemmatizer respectively.
We submitted one run for this task:
IIT P BM 25 statute: This is our only approach to this task. We compute the
BM25 similarity score between a query document and every statute and then
the candidates are returned in decreasing order of similarity score.
4</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Results and Discussion</title>
      <p>This section describes the results obtained in the two tasks by our proposed
approaches. The results obtained in Task 1 are shown in the Table 1. In the Table,
MAP is mean average precision, BPREF is a measure used when the relevance
assessments are not enough and it is suspected that there are many documents
(usually the relevant ones) which are not considered for assessment. In this Table,
the last column i.e. column 5 indicates 1 / rank of the rst relevant document as
provided by the task organizers'. It is basically, Mean Reciprocal Rank used for
exact item search where we are interested in nding *one* (the rst one) correct
answer and not *all* correct ones. The rst run, i.e. IITP BM25 case model
achieved a MAP of 0.0984 and BPREF of 0.0869, which are the 5th among all
23 runs submitted for Task 1 by various teams. In terms of runs submitted by
unique team, this run is in 3rd position in terms of MAP and BFREF.
The results obtained in Task 2 are shown in Table 2. In this task (i.e. Task 2),
we obtain a secure position in the leaderboard.</p>
    </sec>
    <sec id="sec-5">
      <title>Conclusion and Future Work</title>
      <p>This paper presents the working note of our participation in Arti cial Intelligence
for Legal Assistance (AILA 2019) track, which is an associated event of Forum
for Information Retrieval Evaluation (FIRE)- 2019. The shared task de ned two
tasks as follows: viz. i. Identifying relevant prior cases for a given situation ii.
Identifying the most relevant statutes for a given situation. We participated in
both the tasks. We submitted two runs for task1 and one for the Task 2. In Task
1, our models are based on Doc2Vec and BM25. We proposed the BM25 based
model for Task 2. We stood 3rd in Task 1 and secured a moderate position in
the scoreboard of the second task. Our future work including:
{ Development of deep learning based supervised approach. As this kind of
approach itself is very data hungry, we need to increase the volume of the
data.
{ We could make use of several other unsupervised similarity metrics for these
tasks.
{ Contextual embedding followed by attention mechanism might be a good
approach to tackle these tasks. But for all the cases data is the main
bottleneck. We should put our focus on preparing more judicial domain annotated
data for these problems.
{ We could enlarge this dataset by merging the dataset which was released in
Information Retrieval from Legal Documents (IRLeD) - FIRE 2017. That
dataset is in the same line of this track i.e. Arti cial Intelligence for Legal
Assistance (AILA) 2019 dataset.
6</p>
    </sec>
    <sec id="sec-6">
      <title>Acknowledgments</title>
      <p>Mr. Tanik Saikh acknowledges all the co-authors for their contributions. We also
acknowledge the funding agency for the commitment to providing funds.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Bhattacharya</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ghosh</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ghosh</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pal</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mehta</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bhattacharya</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Majumder</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Overview of the FIRE 2019 AILA track: Arti cial Intelligence for Legal Assistance</article-title>
          .
          <source>In: Proceedings of FIRE 2019 - Forum for Information Retrieval Evaluation (December</source>
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Gain</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bandyopadhyay</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Saikh</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ekbal</surname>
            ,
            <given-names>A.:</given-names>
          </string-name>
          <article-title>IITP in coliee@icail 2019: Legal information retrieval using BM25 and BERT</article-title>
          .
          <source>ICAIL '19</source>
          ,
          <string-name>
            <surname>ACM</surname>
          </string-name>
          , New York, NY, USA (06
          <year>2019</year>
          ). https://doi.org/10.13140
          <source>/RG.2.2.28887.32161</source>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Le</surname>
            ,
            <given-names>Q.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mikolov</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Distributed representations of sentences and documents</article-title>
          .
          <source>In: Proceedings of the 31st International Conference on International Conference on Machine Learning - Volume 32</source>
          . pp.
          <article-title>II{1188{II{1196. ICML'14, JMLR</article-title>
          .org (
          <year>2014</year>
          ), http://dl.acm.org/citation.cfm?id=
          <volume>3044805</volume>
          .
          <fpage>3045025</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Mandal</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ghosh</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bhattacharya</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pal</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ghosh</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Overview of the FIRE 2017 irled track: Information retrieval from legal documents</article-title>
          .
          <source>In: Working notes of FIRE 2017 - Forum for Information Retrieval Evaluation</source>
          , Bangalore, India, December 8-
          <issue>10</issue>
          ,
          <year>2017</year>
          . pp.
          <volume>63</volume>
          {
          <issue>68</issue>
          (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Robertson</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zaragoza</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          , et al.:
          <article-title>The probabilistic relevance framework: Bm25 and beyond</article-title>
          .
          <source>Foundations and Trends R in Information Retrieval</source>
          <volume>3</volume>
          (
          <issue>4</issue>
          ),
          <volume>333</volume>
          {
          <fpage>389</fpage>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Rumelhart</surname>
            ,
            <given-names>D.E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hinton</surname>
            ,
            <given-names>G.E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Williams</surname>
            ,
            <given-names>R.J.</given-names>
          </string-name>
          , et al.:
          <article-title>Learning representations by back-propagating errors</article-title>
          .
          <source>Cognitive modeling 5</source>
          (
          <issue>3</issue>
          ),
          <volume>1</volume>
          (
          <year>1988</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>