<!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>Conceptual Model-driven Legal Insights for Stakeholder Decision Making</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Sagar Sunkle</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Krati Saxena</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Vinay Kulkarni</string-name>
          <email>vinay.vkulkarni@tcs.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Tata Consultancy Services Research</institution>
          ,
          <addr-line>Pune 400011</addr-line>
          ,
          <country country="IN">India</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2020</year>
      </pub-date>
      <fpage>31</fpage>
      <lpage>44</lpage>
      <abstract>
        <p>The applicant(s) and the defendant(s), i.e., the parties involved in legal cases, often lack knowledge about the scope of dispute and how it a ects their/courts' decision making. Legal professionals too would like to get a consensus view of the past cases and interpret the facts of the case for their clients. Existing work in the area proposes summarization and legal entity extraction from similar past incidents with the interpretation left to the respective parties. In contrast, we present an approach that correlates the facts of the cases, the verdicts, and the reasons behind those verdicts in the form of easily consumable insights. We propose to use two conceptual models- rst representing a metamodel of legal case insights common across various legal domains and the second, a set of conceptual models of a speci c legal domain under consideration. We use these models to inform case categorization and user pro ling. Then, using a combination of natural language processing and machine learning techniques, we extract pro le-speci c insights across related available past cases. We demonstrate the utility of our approach using examples from two disparate legal domains, parental alienation cases and divorce cases with promising results, including how such insights can aid decision-making of the user.</p>
      </abstract>
      <kwd-group>
        <kwd>Legal Insights</kwd>
        <kwd>Decision-Making</kwd>
        <kwd>Conceptual Modeling</kwd>
        <kwd>Legal Domain</kwd>
        <kwd>Clustering</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>INTRODUCTION</title>
      <p>The parties involved in the court cases depend on legal professionals for the
knowledge about their cases. Usually, lawyers provide insights on cases based
on their understanding and legal knowledge. Searching from a previous case
database and understanding how those cases help or relate to the case in hand
is a tedious job.</p>
      <p>
        The existing systems provide information from previous cases in the form
of summaries or legal entities, interpretation of which requires proper legal
understanding [
        <xref ref-type="bibr" rid="ref13 ref2 ref3 ref5 ref6 ref9">2,3,5,6,9,13</xref>
        ]. Non-legal users cannot use these systems due to the
legalese and a general lack of awareness around statistics about speci c cases.
Ontology-based systems in the legal domain demonstrate promising research
towards creating legal ontologies [
        <xref ref-type="bibr" rid="ref1 ref11 ref4 ref7">11,7,1,4</xref>
        ]. Ontologies on their own do not
contribute to the sense-making for an end-user. With these outputs at hand, users
still need to check the case le if particulars are needed, which is a time and
e ort-intensive process.
      </p>
      <p>We propose a (semi-) automated system to obtain insights from past legal
cases. The involved parties can use this system to get a better awareness of
previous similar cases on their own. Such a system has the potential to help
them in decision-making to maximize their bene t in the legal process. On the
other hand, legal professionals can use this system to pro le their clients or get
general insights on what course to follow in an ongoing or a new case based on
their client's circumstances.</p>
      <p>We present a metamodel of legal cases geared towards insight
categorization and identi cation. The metamodel guides the formation of a set of concept
models of a speci c legal domain. We use these concepts models to create a
categorization of concepts and a set of user pro les. To retrieve insights speci c to
those pro les, we use text searching techniques to pinpoint speci c information
that contributes to the insights. Our overall approach is illustrated in Figure 1.</p>
      <p>Our speci c contributions are twofold:
{ With limited manual intervention, our system generates statistical insights
from past cases in a manner that is easily understandable for both legal and
non-legal stakeholders.
{ The proposed metamodel assists a scheme of categorization generic enough
to apply to any legal domain while being capable of aiding decision-making
of legal stakeholders.</p>
      <p>We organize the paper as follows. We detail our approach in Section 2. In
Section 3, we describe cases from two legal domains, namely parental alienation
and divorce cases. Section 4 applies the system to case datasets of the two legal
domains and discusses results. We review the related work and conclude the
paper in Section 5 and 6, respectively.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Modeling and Generating Legal Insights</title>
      <p>In Figure 1, we refer to the steps involving the generation of a set of concept
models and categorization of metamodel components as information modeling.
The text processing covers various NLP and ML techniques that we use to process
the text of the past cases. The statistical insights system generates insights by
extracting and analyzing relevant spans of text based on the user pro ling system
to produce insights. We describe each of these steps in detail next.
Information Modeling All legal cases deal with con icts between the parties.
The applicant/appellant/plainti presents a complaint or appeal against the
defendant/respondent. Our observations suggest that legal cases mainly comprise
of ve components: the parties involved, the previous verdicts on (an ongoing)
case(s), the facts related to the parties, the appeals made by the parties and the
court verdict. These components lead to a simple conceptual metamodel shown
in Figure 2.</p>
      <p>involves</p>
      <p>LedTo
comprise
consider
resultIn
basedOn</p>
      <p>We observe that di erent countries/states/cities may record the cases with
di erent sections, and those sections may overlap in the indicative content. Our
approach requires that the user maps the speci c set of sections in the cases
under consideration to the above list of sections.</p>
      <p>
        We create a concept model for each of the sections present in the case data
using the metamodel in Figure 2 as the guide. For the aided creation of concept
model based on our approach presented in [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ], we collate the text for each
section from all the past case les available. As described in [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ], the
human-inthe-loop creation involves starting with a seed concept and using the provided
user interface to choose in an ongoing manner the next set of concepts in the
model from the suggestions o ered. It is in this step that the expert, cognizant
of the metamodel, chooses concepts in sync with it. The expert selects a concept
and also adds relevant mention(s). A mention is any reference to the concept in
the text.
      </p>
      <p>At the end of the categorization exercise, we have a categorization dictionary.
We show example concept models for both case studies in Figures 3 and 4 and
categorizations in Figure 5 in later sections.</p>
      <p>User Pro ling As indicated earlier, we bind the categorizations to both the
construction of a user pro le and the generation of insights. For each category
type such as parties or facts, we create simple wh- questions, the options for
which are the category mentions in the categorization dictionary. For instance,
the parties category leads to the question who are the party involved in the case?
and the options presented would be all the mentions of the parties category. We
provide examples of pro ling questions and options based on the category in
Figure 5 in Section 3.</p>
      <p>Text Processing To generate insights from past cases, we need to process
the text of the cases. Usually, the legal text contains long and complicated
sentences with complex syntactical structure. We apply standard text normalization
and segment the text into sentences1.</p>
      <p>The domain expert creates a pattern dictionary from the sentences which is
used to parse the sentences to generate the statistics. Pattern dictionary contains
the text patterns which are indicative of the category mentions. We aid the
determination of these patterns in the sentences using clustering. We use
TFIDF vectors to vectorize the sentences. Then, we create embedded text from
the vectorized text by dimension reduction using principal component analysis2.
Finally, we apply K-Means clustering3 to the embedded text with k=10. The
expert identify the patterns in the sentences and create pattern dictionary. We
show example text patterns in Figure 6 in Section 3.</p>
      <p>Insights Computation We store the text in a Python dataframe. For each
user pro ling question, the user chooses the options from category mentions.
We show the generated questions for both case studies in Figure 7 in Section
3. We parse the text in the dataframe by matching patterns from the pattern
dictionary for the selected options of the category mentions. We compute the
statistics as counts and percentages of each category in the text spans. In Section
4, we show the results for instances of two case studies in Figure 8, wherein a
party is the user and has chosen speci c options to the set of questions that the
system presents.</p>
      <p>In the next section, we begin by describing the two case studies under
consideration.
1 Spacy sentence boundary identi cation https://spacy.io/usage/spacy-101#features
2 Principal component analysis in sklearn https://scikit-learn.org/stable/modules/
generated/sklearn.decomposition.PCA.html
3 K-Means clustering https://scikit-learn.org/stable/modules/generated/sklearn.
cluster.KMeans.html
amend
case
has
presides over</p>
      <p>court
parties
are</p>
      <p>has</p>
      <p>makes
appeal
has</p>
      <p>is
child</p>
      <p>custody
placed with</p>
      <p>placed under costs
foster_care</p>
      <p>supervision
arrangement_between_party_and_child</p>
    </sec>
    <sec id="sec-3">
      <title>Case Studies</title>
      <p>In the following, we brie y describe the two case studies, namely parental
alienation (PA) and divorce cases from Dutch civil court. The reason we choose these
legal domains is that both parental alienation and divorce cases considerably
affect the social and emotional well-being of the involved parties. A system of legal
insights can be bene cial in aiding the parties to understand the characteristics
of such cases, including especially for parties like an alienated parent or a spouse
with a bad marriage.</p>
      <p>For want of space, we show a single curtailed concept model for PA and
divorce cases in Figures 3 and 4 respectively. We make available selected artefacts
for both cases including the section-wise concept models of PA cases4.</p>
      <p>We rst translate the Dutch legal text into English language text using
Google translate API5. We identify the sections present in the les and extract
and collate the text for each section. Using this text, the domain expert create
concept models for each section.</p>
      <p>
        Parental Alienation Cases Parental alienation (PA) is a situation where
the child gets enmeshed with a preferred parent and rejects the relationship from
the other parent without legitimate justi cation [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ].
4 Selected artefacts available at https://github.com/sjrddjtmhkm/cmlcisdm data
5 Google translate API https://translate.google.com/
orders
      </p>
      <p>The concept models of various sections inform us that the parties involved in
PA cases are father, mother, child, institutions (like youth care centres), foster
parents, relatives, and court councils. PA cases revolve around custody of
children entrusted to parents, foster care or institutions, the arrangement of contact
or visitation between parties and the children, the residence of the children and
placement of children under supervision. The identi ed categories are shown in
Figure 3.</p>
      <p>
        Divorce Cases Divorce or dissolution of marriage is the process of
terminating a marital union. The divorce cases include parties such as man, woman,
child, institutions, councils, bank, curator, and notary [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. They also include
marriage/divorce disputes, division of marital property, payments such as child
support, alimony, living expenses and other disputed costs and income,
agreements and settlements between the parties and parental plan for the children.
      </p>
      <p>If the spouses have children, the divorce cases may include PA topics like
the custody of children entrusted to parents, foster care or institutions, the
arrangement of the contact or the visitation between the parties and the children,
the residence of the children, and placement of children under supervision. The
court presides over these cases, orders investigation on the current situations,
announces decision on the appeals and orders the required action from the parties.
The identi ed categories are also shown in Figure 4.</p>
      <p>pronounces
presides over
court</p>
      <p>facts
has
facts_category
case
has
makes
appeal
has
Divorce_case</p>
      <p>has</p>
      <p>Use Pro ling Questions and Insights Generation We show the schematic
of question generation in Figure 5. As indicated earlier in Section 2, we
implement a simple template-based question generation for these concepts. For the
case category, the rule is to add What is in front of the concept. For the who type
of questions, we add who are followed by the concept, followed by involved in the
case?. For the rest of the what type of questions, we add what are the followed by
the concept followed by applicable in your case?. This processing gives us pro ling
questions. We use the resultant list of questions and the categorization
dictionary to obtain responses from the user to create their pro le. In Figure 5, on
the right, we show the categorization dictionary for both PA and divorce cases.</p>
      <p>We generate the count-based results from the normalized and segmented
text by rule-based parsing. The rule-based parsing involves the matching of the
patterns from pattern dictionary for category mentions chosen by the user.
As discussed earlier in Section 2, the domain expert obtain the pattern
dictionary using clustering and principal component analysis. Examples of identi ed
patterns for a few cluster mentions are presented in Figure 6.
Our case datasets include 109 and 102 case les for PA6 and divorce7 cases,
respectively. As described earlier in Section 2, we present a set of questions to
the user(s) who select(s) options applicable to their situation (as in Figure 7).
Figure 8 shows the results obtained for each case study based on the chosen
options in Figure 7.
Case category The rst question asks the user to input the case category.
The options include all the legal domains for which the data is available and
processed, in this case, PA and divorce.</p>
      <p>The resultant statistics show the parties and their occurrence in selected case
category. It also shows the top group of parties that appear together in the cases.
In Figure 8(a) and 8(b), the top-left output shows the count of the parties that
are the general participants in PA or divorce cases.</p>
      <p>Parties contesting the case Next question is Who are the parties involved in
the case?. Based on the option chosen by the user, the output shows the statistics
and the text spans of previous verdicts of the cases where the parties were the
options chosen by the user.</p>
      <p>The top-middle output in Figure 8(a) and 8(b) shows the result for inputs
mother, father, institution and council in PA cases and man, woman and council
in divorce cases. The statistics show what are the portions of each category in
6 Sample le available at https://uitspraken.rechtspraak.nl/inziendocument?id=</p>
      <p>ECLI:NL:GHAMS:2019:44, more les available with other nomenclatures.
7 Divorce cases https://jure.nl/echtscheiding
the previous verdicts in related cases and what parties are involved in what kinds
of previous verdict categories.</p>
      <p>Previous Verdicts The third question is about choosing previous verdicts, if
applicable. User can select None if the user has a new case. Otherwise, the user
chooses other options applicable to his/her case. The top-right output in Figure
8(a) and 8(b) shows the output for question about previous verdicts. Here, the
user chooses residence of the child, arrangement between the party and the child
in PA cases. For divorce cases, the choices were divorce dispute, parental plan,
costs and income.</p>
      <p>The output is text spans of facts and statistics on the facts where previous
verdicts were about the options mentioned above chosen by the user.
Facts related to Parties The fourth question is about the facts of the cases.
The user chooses the facts applicable to their case. Here, the user chooses
residence and arrangement in PA cases. For divorce cases, the user has chosen
divorce, cost, and income.</p>
      <p>These set of choices outputs the text spans of appeals and requests made
by the parties. The bottom-left output in Figure 8(a) and Figure 8(b) show the
percentage of each category spanned by the appeals.</p>
      <p>Appeal made by Parties The nal question asks the user to input the appeal
applicable in their case. Here, the user selects the option of supervision,
custody, and arrangement in PA cases and property, costs, and previous verdict in
divorce cases. Based on the input, the system shows statistics and text of court
decisions/verdicts in selected cases and the reasons for those verdicts as shown
in bottom-middle and bottom-right outputs of Figure 8(a) and 8(b).</p>
      <sec id="sec-3-1">
        <title>Using Insights in Decision-making</title>
        <p>The user can use the above set of results in interpreting similar previous cases
and in decision-making as follows:
Case Category A person who is searching for insights on previous similar cases
gets to know what other parties are involved in a legal domain, which they may
not have considered. For example, a parent going to contest a new case gets to
know that there are institutions, guardians and council involved in PA cases.</p>
        <p>Similarly, a man or woman contesting divorce case gets to know that curator
and bank may be involved in the case. So they can prepare for situations where
other parties may get involved which the user previously did not consider, due
to the court's decision.</p>
        <p>Parties These results show the statistics on previous verdicts. These can help a
user by conveying the possibilities of the court's action. If a case has more than
one hearing, the previous verdicts show the categories where the court's decision
gets pending for review the most.</p>
        <p>For example, in the top middle output of Figure 8(a), user can understand
that placement of a child with an institution, arrangement and previous requests
get pending for a review mostly. Similarly, in the top middle output of Figure
8(b), divorce/marriage disputes and residence of the child gets pending for the
review.</p>
        <p>Previous Verdicts The statistics show the user which general facts are relevant
in a particular domain. The user can decide how to present the facts to the court
based on what was presented in the previous cases. The parties in the statistics
on facts also shed a light on which facts are essential corresponding to each party.</p>
        <p>Statistics in the top right output of Figure 8(a) for PA cases show that mother
and child are involved in all the fact categories in this case. It means that they
play an essential role in the case.</p>
        <p>Other important facts shown relate to these parties like the residence of the
child is with mother and mother is charged with the custody of the child in these
cases. Similarly, in the top right output of Figure 8(b) for divorce cases, most
of the facts categories are about the man. This result shows that facts such as
costs and income of a man are crucial facts. Similarly, the child's residence is
another important fact for the selected cases.</p>
        <p>Facts related to the Parties We can observe in the bottom left output of
Figure 8(a) for PA, previous verdicts announced by the court makes for 57.1%
of the total appeals. The appeal related to the placement of the child under
supervision is another major area of appeal with 20%. In the bottom left output
in Figure 8(b) for divorce cases, appeals about costs, previous verdict, property
and residence spans 31.2%, 25%, 12.5% and 12.5% respectively of all the appeals.</p>
        <p>This result tells the user about the majority of appeals in the selected data.
By looking at the text spans of these appeals, the user can understand what
exact appeals were made for these categories and how they can be presented for
the current case.</p>
        <p>All the statistics mentioned above are simple ways to comprehend what
happens in the cases.</p>
        <p>Appeals made by Parties The nal result in bottom middle and bottom right
outputs of Figure 8(a) and Figure 8(b) informs the user about their standing in
the case.</p>
        <p>Based on the options chosen in the previous questions, this result informs
the user about how many times the appeal was rati ed, annulled or left pending
for review. 50% of the times the decision get annulled for both PA and divorce
cases in Figure 8. For PA, 43.8% decisions get rati ed, and rest is left for review.
For divorce, there is no pending decision; the remaining 50% cases get rati ed.</p>
        <p>Reasons of the verdict are also shown in bottom right outputs of Figure 8(a)
and Figure 8(b). Reasons can advise the user about all the steps a user can
take to get their appeals rati ed. For example, in Figure 8(a) for PA cases, the
statistics show that previous judgments, communication between parties and
child development and well-being are some of the critical points in
decisionmaking by the court constituting 27.6%, 14.41% and 11.57% each respectively.</p>
        <p>In Figure 8(b) for divorce cases, the main reasons for the verdict include
previous judgement, costs, property and income of the parties spanning 38.1%,
21.03%, 14.02% and 5.54% of all the reasons. So the user can develop a case
around these points to get a favourable result. User can present evidence on these
categories that prove their case or disproves the opponent's case to maximize
their bene t.
4.3</p>
      </sec>
      <sec id="sec-3-2">
        <title>Limitations and Future Work</title>
        <p>In the following, we brie y discuss the limitations of our approach and way
forward.</p>
        <p>{ The output shows statistics and also provides an option to view all the text
spans about a chosen categorization. The text output may contain several
text spans and may become cumbersome for the user to go through. In
future, we plan to extract more ne-grained information from the text spans.
For example, the residence category will return all the sentences related to
residence. Still, the user may require speci c information such as the exact
location for the residence of the child. Extracting such ne-grained
information is non-trivial. We can train structured prediction machine learning
models, but such models require extensive annotated data.
{ Users esp. non-legal users may nd pieces of information di cult to
comprehend even though contextualized to their pro le. In ongoing work, we plan to
present recommendations that suggest a possible course of action to the user.
As an example, consider possible decision making suggestions from Section
4.2 based on case category and parties. In the examples we provided, we
suggest the user (partaking in a divorce case) become aware of the involvement
of alternate parties and (in case of PA cases) the fact that the said cases get
pending for review. We can prepare an individual recommendation for the
rst example as follows: your case may involve bank and curator as alternate
parties; it is recommended to enquire and plan about the inclusion of such
parties. For the second example, the recommendation would be, your case
involves a child with an institution. Such cases get pending for a review;
it is recommended to include this in defence or plan for the duration. We
can treat parts of these recommendations as sections of a template in which
certain blanks are lled with the contextualized information. By combining
all of the recommendations for a particular case, it is possible to create a
narrative applicable to the case considering the case categories, the parties,
previous verdicts, and facts and appeals.
5</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Related Work</title>
      <p>
        Ontologies in legal domain Ontologies and modelling in legal domain is
widely researched topic. Several papers describe processes to create legal
ontologies [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] and capture the legal knowledge in several ways. Most work on
legal ontologies focuses on designing part of the ontology and models and how
they can be used for tasks such as document classi cation, search and retrieval
tasks. Alternatively, our approach provides a way to create conceptual model
based on legal case metamodel and further use it to generate text spans and
statistics based on the user pro le.
      </p>
      <p>
        Text Summarization Considerable research exists on legal text
summarization [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. Farzindar et al. [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] created LetSum system which uses a linguistic
approach to extract summaries in the form of tables from Canadian legal cases.
Using this, Chieze et al. [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] developed DecisionExpress which can extract
information related to judges, tribunals, subject of the information, conclusions
of judgment and a brief description of a case in both English and French for
Canadian legal cases.
      </p>
      <p>Most legal summarization works produce summaries which could be
considered a coarser version of insights that our system generates. Besides creating
summaries of entire documents, these works do not distinguish aspects
corresponding to our metamodel. Finally, unlike our approach, these works do not
enable customizing the summaries for a given user pro le.</p>
      <p>
        Information Extraction Most legal information extraction work focuses on
techniques for extraction rather than a conceptual scheme for arranging the
extracted information in a manner useful for decision-making. For instance, several
works focus on document segmentation, and legal entity extraction [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], legal text
indexing and argument extraction [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ], and legal event extraction [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>We distinguish our approach from the works cited above in terms of the
conceptual framework that our approach o ers. Besides, the focus of our approach is
on generating easily understandable insights even for non-legal users, including
parties involved in the legal cases.
6</p>
    </sec>
    <sec id="sec-5">
      <title>CONCLUSION</title>
      <p>Past legal cases can provide insights such as, which parties generally get involved,
for speci c facts what were the previous verdicts, and which reasons cause given
decisions. We presented a conceptual model-driven approach that enables both
non-legal parties and legal professionals to obtain such insights by responding
to a set of pro ling questions. The users can consider these insights for
decisionmaking. Our results on two case datasets on parental alienation and divorce
cases prove the utility of our approach. We continue to work on extracting and
presenting more ne-grained legal insights.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Alexander</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Lkif core: Principled ontology development for the legal domain. Law, ontologies and the semantic web: channelling the legal</article-title>
          <source>information ood 188</source>
          ,
          <issue>21</issue>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2. de Araujo,
          <string-name>
            <given-names>D.A.</given-names>
            ,
            <surname>Rigo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.J.</given-names>
            ,
            <surname>Barbosa</surname>
          </string-name>
          ,
          <string-name>
            <surname>J.L.V.</surname>
          </string-name>
          :
          <article-title>Ontology-based information extraction for juridical events with case studies in brazilian legal realm</article-title>
          .
          <source>Arti cial Intelligence and Law</source>
          <volume>25</volume>
          (
          <issue>4</issue>
          ),
          <volume>379</volume>
          {
          <fpage>396</fpage>
          (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Bommarito</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Michael</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Katz</surname>
            ,
            <given-names>D.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Detterman</surname>
            ,
            <given-names>E.M.:</given-names>
          </string-name>
          <article-title>Lexnlp: Natural language processing and information extraction for legal and regulatory texts</article-title>
          . arXiv preprint arXiv:
          <year>1806</year>
          .
          <volume>03688</volume>
          (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Breuker</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Elhag</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Petkov</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Winkels</surname>
          </string-name>
          , R.:
          <article-title>Ontologies for legal information serving and knowledge management</article-title>
          .
          <source>In: Legal Knowledge and Information Systems</source>
          ,
          <year>Jurix 2002</year>
          :
          <article-title>The Fifteenth Annual Conference</article-title>
          . pp.
          <volume>1</volume>
          {
          <issue>10</issue>
          (
          <year>2002</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Chieze</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Farzindar</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lapalme</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          :
          <article-title>An automatic system for summarization and information extraction of legal information</article-title>
          .
          <source>In: Semantic processing of legal texts</source>
          , pp.
          <volume>216</volume>
          {
          <fpage>234</fpage>
          . Springer (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Farzindar</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lapalme</surname>
          </string-name>
          , G.:
          <article-title>Letsum, an automatic legal text summarizing system. Legal knowledge and information systems</article-title>
          , JURIX pp.
          <volume>11</volume>
          {
          <issue>18</issue>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Fawei</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pan</surname>
            ,
            <given-names>J.Z.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kollingbaum</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wyner</surname>
            ,
            <given-names>A.Z.:</given-names>
          </string-name>
          <article-title>A semi-automated ontology construction for legal question answering</article-title>
          .
          <source>New Generation Computing</source>
          <volume>37</volume>
          (
          <issue>4</issue>
          ),
          <volume>453</volume>
          {
          <fpage>478</fpage>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Hetherington</surname>
            ,
            <given-names>E.M.:</given-names>
          </string-name>
          <article-title>Divorce: a child's perspective</article-title>
          .
          <source>American</source>
          psychologist
          <volume>34</volume>
          (
          <issue>10</issue>
          ),
          <volume>851</volume>
          (
          <year>1979</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Kanapala</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pal</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pamula</surname>
          </string-name>
          , R.:
          <article-title>Text summarization from legal documents: a survey</article-title>
          .
          <source>Arti cial Intelligence Review</source>
          <volume>51</volume>
          (
          <issue>3</issue>
          ),
          <volume>371</volume>
          {
          <fpage>402</fpage>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Kelly</surname>
            ,
            <given-names>J.B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Johnston</surname>
            ,
            <given-names>J.R.:</given-names>
          </string-name>
          <article-title>The alienated child: A reformulation of parental alienation syndrome</article-title>
          .
          <source>Family court review 39(3)</source>
          ,
          <volume>249</volume>
          {
          <fpage>266</fpage>
          (
          <year>2001</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Soares</surname>
            ,
            <given-names>A.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Martins</surname>
            ,
            <given-names>P.V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>da Silva</surname>
            ,
            <given-names>A.R.</given-names>
          </string-name>
          :
          <article-title>Legallanguage: A domain-speci c language for legal contexts</article-title>
          . In: Enterprise Engineering Working Conference. pp.
          <volume>33</volume>
          {
          <fpage>51</fpage>
          . Springer (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Sunkle</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kholkar</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kulkarni</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          :
          <article-title>Comparison and synergy between factorientation and relation extraction for domain model generation in regulatory compliance</article-title>
          .
          <source>In: Conceptual Modeling - 35th International Conference, ER</source>
          <year>2016</year>
          , Gifu, Japan,
          <source>November 14-17</source>
          ,
          <year>2016</year>
          ,
          <source>Proceedings. Lecture Notes in Computer Science</source>
          , vol.
          <volume>9974</volume>
          , pp.
          <volume>381</volume>
          {
          <issue>395</issue>
          (
          <year>2016</year>
          ). https://doi.org/10.1007/978-3-
          <fpage>319</fpage>
          -46397-129, http://dx.doi.
          <source>org/10.1007/978-3-319-46397-1 29</source>
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Wyner</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mochales-Palau</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Moens</surname>
            ,
            <given-names>M.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Milward</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Approaches to text mining arguments from legal cases</article-title>
          .
          <source>In: Semantic processing of legal texts</source>
          , pp.
          <volume>60</volume>
          {
          <fpage>79</fpage>
          . Springer (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>