<!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>Applying Argument Extraction to Improve Legal Information Retrieval</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Kevin D. Ashley</string-name>
          <email>ashley@pitt.edu</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>University of Pittsburgh School of Law Pittsburgh</institution>
          ,
          <addr-line>Pennsylvania, USA 15260</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Argument extraction techniques can likely improve legal information retrieval. Any effort to achieve that goal should take into account key features of legal reasoning such as the importance of legal rules and concepts, support and attack relations among claims, and citation of authoritative sources. Annotation types reflecting these key features will help identify the roles of textual elements in retrieved legal cases in order to better inform assessments of relevance for users' queries. As a result, legal argument models and argument schemes will likely play a central part in the text annotation type system.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1 Introduction</title>
      <p>With improved prospects for automatically
extracting arguments from text, we are
investigating whether and how argument extraction can
improve legal information retrieval (IR). An
immediate question in that regard is the role that argument
models and argument schemes will play in
achieving this goal.</p>
      <p>
        For some time, researchers in Artificial
Intelligence and Law have developed argument models,
formal and dialectical process models to describe
arguments and their relations. They have also
implemented these models in computer programs
that construct legal arguments. Some of these
models employ argument schemes to provide
semantics and describe reasonable arguments. Each
scheme corresponds to a typical domain-specific
inference sanctioned by the argument, a kind of
prima facie reason for believing the argument’s
conclusion. See
        <xref ref-type="bibr" rid="ref12 ref17">(Prakken, 2005, p. 234)</xref>
        .
      </p>
      <p>By and large, however, these argument models
and schemes and their computational
implementations have not had much of a practical effect on
legal practice. A primary reason for this is the
well-known bottleneck in representing knowledge
from the legal texts (e.g., statutes, regulations, and
cases) that play such an important role in legal
practice in a form so that the the computational
implementations can reason with them.</p>
      <p>Meanwhile, legal information retrieval systems
have proven to be highly functional. They
provide legal practitioners with convenient access
to millions of legal texts without relying on
argument models or schemes, relying instead on
Bayesian statistical inference based on term
frequency. Users of legal information systems can
submit queries in the form of a natural language
description of a desired fact pattern and retrieve
numerous relevant cases.</p>
      <p>
        Useful as they are, however, legal information
retrieval systems do not provide all of the
functionality that practitioners could employ. What
IR system users often want “is not merely IR,
but AR”, that is, “argument retrieval: not merely
sentences with highlighted terms, but arguments
and argument-related information. For example,
users want to know what legal or factual issues the
court decided, what evidence it considered
relevant, what outcomes it reached, and what reasons
it gave.”
        <xref ref-type="bibr" rid="ref19 ref2 ref3">(Ashley and Walker, 2013a)</xref>
        .
      </p>
      <p>
        Recently, IBM announced its Debater project,
an argument construction engine which, given a
corpus of unstructured text like Wikipedia, can
automatically construct a set of relevant pro/con
arguments phrased in natural language. Built upon
the foundation of IBM’s Jeopardy-game-winning
Watson question answering system, the advent of
Debater raises some interesting related questions.
A central hypothesis of the Watson project was
to answer questions based on shallow syntactic
knowledge and its implied semantics. This was
preferred to formally represented deep semantic
knowledge, the acquisition of which is difficult
and expensive
        <xref ref-type="bibr" rid="ref8">(Fan et al., 2012)</xref>
        . If Debater is
applied to legal domains (See, e.g.,
        <xref ref-type="bibr" rid="ref4">(Beck, 2014)</xref>
        ),
one wonders to what extent the same will be true
of Debater. In particular, to what extent will
explicit argumentation models and their schemes for
the legal domain be necessary or useful for the
effort to extract legal arguments? And, can
techniques in Debater be adapted to improve legal IR?
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>Related Work</title>
      <p>
        The seminal work on extracting arguments and
argument-related information from legal case
decisions is
        <xref ref-type="bibr" rid="ref16 ref9">(Mochales and Moens, 2011)</xref>
        .
Operationally, the authors defined an argument as “a set
of propositions, all of which are premises except,
at most, one, which is a conclusion. Any argument
follows an argumentation scheme. . . .” Using
machine learning based on manually classified
sentences from the Araucaria corpus, including court
reports, they achieved good performance on
classifying sentences as propositions in arguments or
not and classifying argumentative propositions as
premises or conclusions. Given a limited set of
documents, their manually-constructed rule-based
argument grammar also generated argument tree
structures
        <xref ref-type="bibr" rid="ref16 ref9">(Mochales and Moens, 2011)</xref>
        .
      </p>
      <p>
        In identifying argumentative propositions,
Mochales and Moens achieved accuracies of 73%
and 80% on two corpora, employing
domaingeneral features (including, e.g., each word, pairs
of words, pairs and triples of successive words,
parts of speech including adverbs, verbs, modal
auxiliaries, punctuation, keywords indicating
argumentation, parse tree depth and number of
subclauses, and certain text statistics.) For
classifying argumentative propositions as premises or
conclusions, their features included the sentence’s
length and position in the document, tense and
type of main verb, previous and successive
sentences’ categories, a preprocessing
classification as argumentative or not, and the type of
rhetorical patterns occurring in the sentence and
surrounding sentences (i.e., Support, Against,
Conclusion, Other or None). Additional features,
more particular to the legal domain included
whether the sentence referred to or defined a legal
article, the presence of certain argumentative
patterns (e.g. “see”, “mutatis mutandis”, “having
reached this conclusion”, “by a majority”) and
whether the agent of the sentence is the plaintiff,
the defendant, the court or other
        <xref ref-type="bibr" rid="ref16 ref9">(Mochales and
Moens, 2011)</xref>
        .
      </p>
      <p>
        Factors, stereotypical fact patterns that
strengthen or weaken a side’s argument in a legal
claim, have been identified in text automatically.
Using a HYPO-style CBR program and an IR
system relevance feedback module, the SPIRE
program retrieved legal cases from a text corpus
and highlighted passages relevant to bankruptcy
law factors
        <xref ref-type="bibr" rid="ref5">(Daniels and Rissland, 1997)</xref>
        . The
SMILE+IBP program learned to classify case
summaries in terms of applicable trade secret
law factors
        <xref ref-type="bibr" rid="ref1">(Ashley and Bru¨ninghaus, 2009)</xref>
        ,
analyzed automatically classified squibs of new
cases, predicted outcomes, and explained the
predictions.
        <xref ref-type="bibr" rid="ref18 ref24">(Wyner and Peters, 2010)</xref>
        presents a
scheme for annotating 39 trade secret case texts
with GATE in terms of finer grained components
(i.e., factoroids) of a selection of factors.
      </p>
      <p>
        Using an argument model to assist in
representing cases for conceptual legal information retrieval
was explored in
        <xref ref-type="bibr" rid="ref6">(Dick and Hirst, 1991)</xref>
        . More
recently, other researchers have addressed automatic
semantic processing of case decision texts for
legal IR, achieving some success in automatically:
assigning rhetorical roles to case sentences
based on 200 manually annotated Indian
decisions
        <xref ref-type="bibr" rid="ref18 ref24">(Saravanan and Ravindran, 2010)</xref>
        ,
categorizing legal cases by abstract
Westlaw categories (e.g., bankruptcy, finance and
banking)
        <xref ref-type="bibr" rid="ref20">(Thompson, 2001)</xref>
        or general
topics (e.g., exceptional services pension,
retirement)
        <xref ref-type="bibr" rid="ref12">(Gonc¸alves and Quaresma, 2005)</xref>
        ,
extracting treatment history (e.g., “affirmed”,
“reversed in part”)
        <xref ref-type="bibr" rid="ref14">(Jackson et al., 2003)</xref>
        ,
determining the role of a sentence in the legal
case (e.g., as describing the applicable law or
the facts)
        <xref ref-type="bibr" rid="ref13">(Hachey and Grover, 2006)</xref>
        ,
extracting offenses raised and legal principles
applied from criminal cases to generate
summaries
        <xref ref-type="bibr" rid="ref21">(Uyttendaele et al., 1998)</xref>
        ,
extracting case holdings
        <xref ref-type="bibr" rid="ref15">(McCarty, 2007)</xref>
        ,
and
extracting argument schemes from the
Araucaria corpus such as argument from example
and argument from cause to effect
        <xref ref-type="bibr" rid="ref16 ref9">(Feng and
Hirst, 2011)</xref>
        .
      </p>
      <p>
        We aim to develop and evaluate an integrated
approach using both semantic and pragmatic
(contextual) information to retrieve arguments from
legal texts in order to improve legal information
retrieval. We are working with an underlying
argumentation model and its schemes, the Default
Logic Framework (DLF), and a corpus of U.S.
Federal Claims Court cases
        <xref ref-type="bibr" rid="ref19 ref2 ref22 ref23 ref3">(Walker et al., 2011;
Walker et al., 2014; Ashley and Walker, 2013a)</xref>
        .
Like
        <xref ref-type="bibr" rid="ref16 ref9">(Mochales and Moens, 2011)</xref>
        and
        <xref ref-type="bibr" rid="ref19">(Sergeant,
2013)</xref>
        , we plan to:
1. Train an annotator to automatically identify
propositions in unseen legal case texts,
2. Distinguish argumentative from
nonargumentative propositions and classify them
as premises or conclusions,
3. Employ rule-based or machine learning
models to construct argument trees from unseen
cases based on a manually annotated training
corpus, but also to
4. Use argument trees to improve legal
information retrieval reflecting the uses of
propositions in arguments.
      </p>
      <p>Before sketching our approach for the legal
domain, however, we note that IBM appears to
have developed more domain independent
techniques for identifying propositions in documents
and classifying them as premises in its Debater
system.1</p>
      <p>On any topic, the Debater’s task is to “detect
relevant claims” and return its “top predictions for
pro claims and con claims.” On inputting the topic,
“The sale of violent videogames to minors should
be banned,” for example, Debater:
(1) scanned 4 million Wikipedia articles,
(2) returned the 10 most relevant articles,
(3) scanned the 3000 sentences in those 10
articles,</p>
      <p>(4) detected those sentences that contained
“candidate claims”,
(5) “identified borders of candidate claims”,
(6) “assessed pro and con polarity of candidate
claims”,</p>
      <p>1See, e.g., http://finance.yahoo.com/blogs/
the-exchange/ibm-unveils-a-computerthan-can-argue-181228620.html. A demo
appears at the 45 minute mark:
http://io9.com/ibmswatson-can-now-debate-its-opponents1571837847.</p>
      <p>(7) “constructed a demo speech with top claim
predictions”, and
(8) was then “ready to deliver!”</p>
      <p>Figure 1 shows an argument diagram
constructed manually from the video recording of
Debater’s oral output for the example topic.
3</p>
    </sec>
    <sec id="sec-3">
      <title>Key Elements of Legal Argument</title>
      <p>Debater’s argument regarding banning violent
video games is meaningful but compare it to the
legal argument concerning a similar topic in
Figure 2. The Court in Video Software Dealers
Assoc. v. Schwarzenegger, 556 F. 3d 950 (9th
Cir. 2009), addressed the issue of whether
California (CA ) Civil Code sections 1746-1746.5 (the
“Act”), which restrict sale or rental of “violent
video games” to minors, were unconstitutional
under the 1st and 14th Amendments of the U.S.
Constitution. The Court held the Act unconstitutional.</p>
      <p>As a presumptively invalid content-based
restriction on speech, the Act is subject to strict scrutiny
and the State has not demonstrated a compelling
interest.</p>
      <p>In particular, the Court held that CA had not
demonstrated a compelling government interest
that “the sale of violent video games to minors
should be banned.” Figure 2 shows excerpts from
the portion of the opinion in which the Court
justifies this conclusion. The nodes contain
propositions from that portion and the arcs reflect the
explicit or implied relations among those
propositions based on a fair reading of the text.</p>
      <p>The callout boxes in Figure 2 highlight some
key features of legal argument illustrated in the
Court’s argument:
1. Legal rules and concepts govern a court’s
de</p>
      <p>cision of an issue.
2. Standards of proof govern a court’s
assess</p>
      <p>ment of evidence.
3. Claims have support / attack relations.
4. Authorities are cited (e.g., cases, statutes).
5. Attribution information signals or affects
judgments about belief in an argument (e.g.,
“the State relies”).
6. Candidate claims in a legal document have
different plausibility.</p>
      <p>The  sale  of  violent  videogames  to  minors  should  be  banned.  </p>
      <sec id="sec-3-1">
        <title>Pro:    Exposure  to  violent  </title>
        <p>videogames  results  in  increased  
physiological  arousal,  aggression-­‐
related  thoughts  and  feelings,  as  
well  as  decreased  pro-­‐social  
behavior.  
Pro:  In  addiAon  these  violent  games  or  
lyrics  actually  cause  adolescents  to  
commit  acts  of  real  life  aggression.  
Con:  On  the  other  hand,  I  would  like  to  
note  the  following  claims  that  oppose  
the  topic.  Violence  in  videogames  is  
not  causally  linked  with  aggressive  
tendencies.    
Con:  In  addiAon,  most  children  who  play  
violent  videogames  do  not  have  
problems  </p>
      </sec>
      <sec id="sec-3-2">
        <title>Pro:  Finally,  violent  video  games  can   increase  children’s  aggression.   Con:  Finally,  video  game  play  is  part  of  an   adolescent  boy’s  normal  social  seDng.  </title>
        <p>Although the argument diagrams in Figures 1
and 2 address nearly the same topic and share
similar propositions, the former obviously lacks these
features that would be important in legal argument
(and, as argued later, important in using extracted
arguments to improve legal IR). Of course, on one
level this is not surprising; the Debater argument
is not and does not purport to be a legal argument.</p>
        <p>On the other hand, given the possibility of
applying Debater to legal applications and
argumentation, it would seem essential that it be able to
extract such key information. In that case, the
question is the extent to which explicit argument
models and argument schemes of legal reasoning
would be useful in order to assist with the
extraction of the concepts, relationships, and
information enumerated above and illustrated in Figure 2.
4</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Default-Logic Framework</title>
      <p>Vern Walker’s Default Logic Framework (DLF)
is an argument model plus schemes for
evidencebased legal arguments concerning compliance
with legal rules. At the Research Laboratory for
Law, Logic and Technology (LLT Lab) at
Hofstra University, researchers have applied the DLF to
model legal decisions by Court of Federal Claims
“Special Masters” concerning whether claimants’
compensation claims comply with the
requirements of a federal statute establishing the National
Vaccine Injury Compensation Program. Under the
Act, a claimant may obtain compensation if and
only if the vaccine caused the injury.</p>
      <p>In order to establish causation under the rule
of Althen v. Secr. of Health and Human
Services, 418 F.3d 1274 (Fed.Cir. 2005), the
petitioner must establish by a preponderance of the
evidence that: (1) a “medical theory causally
connects” the type of vaccine with the type of injury,
(2) there was a “logical sequence of cause and
effect” between the particular vaccination and the
particular injury, and (3) a “proximate temporal
relationship” existed between the vaccination and
the injury. Walker’s corpus comprises all
decisions in a 2-year period applying the Althen test of
causation-in-fact (35 decision texts, 15-40 pages
per decision). In these cases, the Special Masters
decide which evidence is relevant to which issues
of fact, evaluate the plausibility of evidence in the
legal record, organize evidence and draw
reasonable inferences, and make findings of fact.</p>
      <p>The DLF model of a single case “integrates
numerous units of reasoning” each “consisting of one
5.  a8ribu9on  </p>
      <p>
        info  
3.  support  /  
a8ack  rela9ons  
1.  rule  and  
legal  concepts    
6.  plausibility  
conclusion and one or more immediately
supporting reasons (premises)” and employing four types
of connectives (min (and), max (or), evidence
factors, and rebut)
        <xref ref-type="bibr" rid="ref23">(Walker et al., 2014)</xref>
        . For example,
Figure 3 shows an argument diagram representing
the excerpt of the the DLF model of the special
master’s finding in the case of Cusati v. Secretary
of Health and Human Services, No. 99-0492V
(Office of Special Masters, United States Court
of Federal Claims, September 22, 2005)
concerning whether the first Althen condition for showing
causation-in-fact is satisfied.
      </p>
      <p>The main point is that the DLF model of a
legal argument and its argument schemes represent
the above-enumerated key features of legal
argument. As illustrated in the callout boxes of Figure
3, the model indicates: (1) the 1st Althen rule and
causation-in-fact concept that govern the decision
of the causation issue, (2) the preponderance of
evidence standard of proof governing the court’s
assessment, (3) support relations among the
propositions, the Special Master having recorded no
counterarguments, (4) citation to the statute, 42 USC
300aa-11(c)(1)(C)(ii)), and to the Althen and
Shyface case authorities, (5) some attribution
information that signals judgments about the Special
Master’s belief in an argument (e.g., “Dr. Kinsbourne
and Dr. Kohrman agree”), and (6) four factors that
increase plausibility of the claim of causation.
5</p>
    </sec>
    <sec id="sec-5">
      <title>Legal Argument and Legal IR</title>
      <p>
        Legal decisions contain propositions and
arguments how to “prove” them. Prior cases provide
examples of how to make particular arguments in
support of similar hypotheses and of kinds of
arguments that have succeeded, or failed, in the past.
Consider a simple query discussed in
        <xref ref-type="bibr" rid="ref19 ref2 ref3">(Ashley and
Walker, 2013a)</xref>
        : Q1: “MMR vaccine can cause
intractable seizure disorder and death.”
      </p>
      <p>An attorney/user in a new case where an injury
followed an MMR vaccination might employ this
query to search for cases where such propositions
had been addressed. Relevant cases would add
confidence that the propositions and
accompany1.  rule  and  </p>
      <p>legal  
concepts    
OR  [2  of  2]  :  OFF-­‐TABLE  
INJURY:  The  "causa=on-­‐
in-­‐fact"  condi=on  is  
sa=sfied  (Althen,  418  F.
3d  at  1278,  1281).    </p>
      <p>3.  support  /  
aYack  rela7ons  
(no  aYacks  here)  </p>
      <p>AND  [1  of  2]  :  The  injury  of  
Eric  Fernandez  "was  [or  
were]  caused  by"  the  MMR  
vaccine  received  in  the  
vaccina=on  on  November  
5,  1996  (42  USC  
300aa-­‐11(c)(1)(C)(ii)).      
AND  [1  of  3]  :  (1)  
A  “medical  
theory  causally  
connect[s]”  the  
vaccina7on  on  
11-­‐5-­‐96  and  an  
intractable  
seizure  disorder  
and  death  
(Althen,  418  F.3d  
at  1278).    </p>
      <p>Q1  
"MMR  vaccine  
causes  fever"  
and  "fever  
causes  
seizures."  "Ms.  
Cusa7  has  
provided  more  
than  
preponderant  
evidence".    
6.  plausibility  
the  MMR  vaccine  was  "not  only  a  
but-­‐for  cause"  of  an  intractable  
seizure  disorder  and  death,  "but  
also  a  substan=al  factor  in  
bringing  about"  an  intractable  
seizure  disorder  and  death  
(Shyface,  165  F.3d  at  1352-­‐53;  
Althen,  418  F.3d  at  1278).    
4.  cita7on  of  
authori7es  
FACTOR  [1  of  4]  :  "MMR  
vaccine  causes  fever."  
Dr.  Kinsbourne  and  Dr.  
Kohrman  agree  that  
MMR  vaccine  causes  
fever.  
FACTOR  [2  of  
4]  :"[F]ever  causes  
seizures."  Dr.  
Kinsbourne  and  Dr.  
Kohrman  agree  that  
fever  causes  seizures.  
FACTOR  [3  of  4]  :"[A]  
child  who  suffers  a  
complex  febrile  seizure  
has  a  greater  chance  of  
developing  epilepsy.”  
FACTOR  [4  of  4]  :  "[T]he  
medical  literature  ...  
do[es]  not  assist  the  
special  master  in  
evalua7ng  Ms.  Cusa7's  
'legal  cause'  claim."  
ing arguments were reasonable and had been
successful.</p>
      <p>Importantly, the cases retrieved will be more
relevant to the extent that the proposition is used in
a similar argument. That is, they will be more
relevant to the extent that the proposition plays roles
in the case arguments similar to the role in which
the attorney intends to use it in an argument about
the current case.</p>
      <p>An argument diagram like that of Figure 3 can
illustrate the effect of the six key elements of
legal reasoning illustrated above on how relevant a
retrieved case is to a user’s query. The diagram
shows a legal argument in which the proposition
corresponding to Q1 plays a role in the Cusati case
as an evidence-based finding of the Special
Master, namely, that “MMR vaccine causes fever” and
“fever causes seizures.”</p>
      <p>Such diagrams have a “legal rule-oriented”
direction (i.e., to the left in Figure 3) and an
“evidentiary factors-oriented” direction (i.e., to the right
in this diagram). For instance, an attorney whose
client sustained seizures after receiving the MMR
vaccine probably knows that he/she will have to
satisfy a requirement of causation. The attorney
may not know, however, what legal standard
defines the relevant concept of causation or what
legal authority may be cited as an authoritative
source of the standard. In that situation, retrieved
cases will likely be more relevant to the extent that
that they fill in the legal rule-oriented direction,
relative to a proposition similar to the one marked
“Q1”, with legal rules about the concept of
causation and citations to their authoritative sources.</p>
      <p>If the attorney is unsure of the kinds of evidence
that an advocate should employ in convincing a
Special Master to make the finding of fact on
causation or of the relevant standard of proof for
assessing that evidence of causation, retrieved cases
will be more relevant to the extent that they fill in
the evidentiary factors-oriented direction, relative
to a proposition similar to the one marked “Q1”,
with evidentiary factors and an identification of
the standard of proof.</p>
      <p>The attorney may be interested in better
understanding how to improve the plausibility of a
proposition about causation as an evidence-based
finding. Cases will be more relevant to the extent
that they contain evidentiary factors that support
such a finding. An attorney interested in
attacking the plausibility of the evidence-based finding
might be especially interested in seeing cases
involving examples of evidentiary factors that attack
such a finding.</p>
      <p>Finally, the cases will be more relevant to
the extent that the proposition similar to the one
marked “Q1” concerning MMR vaccine’s causing
injury is attributable to the Special Master as
opposed merely to some expert witness’s statement.
6</p>
    </sec>
    <sec id="sec-6">
      <title>Specifying/Determining Propositions’</title>
    </sec>
    <sec id="sec-7">
      <title>Argument Roles</title>
      <p>The importance of a proposition’s argument role
in matching retrieved cases to users’ queries raises
two questions: (1) How does the user specify the
target propositions and their argumentative roles
in which he is interested? (2) How does a
program determine the roles that propositions play in
retrieved case arguments?</p>
      <p>An argument diagram like that of Figure 3 may
play a role in enabling users to specify the
arguments and propositions in which they are
interested. One can imagine a user’s inputting a query
by employing a more abstract version of such a
diagram. For instance, in the Query Input Diagram
of Figure 4, the nodes are labeled with, or refer to,
argument roles. These roles include:
Legal Rule: sentences that state a legal rule in the
abstract, without applying the rule to the
particular case being litigated
Ruling/Holding: sentences that apply a legal rule
to decide issues presented in the particular
case being litigated</p>
    </sec>
    <sec id="sec-8">
      <title>Evidence-Based Finding: sentences that report</title>
      <p>a trier-of-fact’s ultimate findings regarding
facts material to the particular case being
litigated</p>
    </sec>
    <sec id="sec-9">
      <title>Evidence-Based Reasoning: sentences that re</title>
      <p>port the trier-of-fact’s reasoning in assessing
the relevant evidence and reaching findings
regarding facts material to the particular case
being litigated (e.g., evidentiary factors)
Evidence: sentences that describe any type of
evidence legally produced in the particular
case being litigated, as part of the proof
intended to persuade the trier-of-fact of alleged
facts material to the case (e.g., oral testimony
of witnesses, including experts on technical
matters; documents, public records,
depositions; objects and photographs)
Citation: sentences that credit and refer to
authoritative documents and sources (e.g., court
decisions (cases), statutes, regulations,
government documents, treaties, scholarly
writing, evidentiary documents)</p>
      <p>In the “text”, “concept”, and “citation” slots of
the appropriate nodes of the query input diagram,
Figure 4, users could specify the propositions,
concepts, or citations that they know or assume
and check the targeted nodes in the directions
(rule-oriented or evidentiary-factors-oriented) or
ranges that they hope to fill through searching for
cases whose texts satisfy the diagram’s
argumentrelated constraints. In effect, the diagram will
guide the IR system in ranking the retrieved cases
for relevance and in highlighting their relevant
parts.</p>
      <p>Regarding the second question, concerning how
a program will determine propositions’ argument
roles in case texts, that is the third task that
Mochales and Moens addressed with a rule-based
grammar applied to a small set of documents.
While their rules employed some features
particular to legal argument, (e.g., whether a sentence
referred to a legal article) one imagines that
additional features would be needed, pertaining to
legal argument or to the regulated domain of
interest. These features would become the
predicates of additional grammar rules or be annotated
in training cases for purposes of machine learning.</p>
      <p>The legal argument roles listed above are a first
cut at a more comprehensive enumeration of the
types of legal argument features with which to
annotate legal case texts in an Unstructured
Information Management Architecture (UIMA)
annotation pipeline for purposes of extracting argument
information and improving legal IR.</p>
      <p>
        UIMA, an open-source Apache framework, has
been deployed in several large-scale
governmentsponsored and commercial text processing
applications, most notably, IBM’s Watson question
answering system
        <xref ref-type="bibr" rid="ref7">(Epstein et al., 2012)</xref>
        . A UIMA
pipeline is an assemblage of integrated text
annotators. The annotators are “a scalable set of
cooperating software programs, . . . , which assign
semantics to some region of text”
        <xref ref-type="bibr" rid="ref11">(Ferrucci, 2012)</xref>
        ,
and “analyze text and produce annotations or
assertions about the text” (Ferrucci et al., 2010, p.
74).
      </p>
      <p>
        A coordinated type system serves as the basis
of communication among these annotators; a type
system embodies a formalization of the
annotators’ analysis input and output data
        <xref ref-type="bibr" rid="ref7">(Epstein et al.,
2012, p. 3)</xref>
        . In
        <xref ref-type="bibr" rid="ref2 ref3">(Ashley and Walker, 2013b)</xref>
        and
        <xref ref-type="bibr" rid="ref19 ref2 ref3">(Ashley and Walker, 2013a)</xref>
        the authors elaborate
three additional bases for annotations, which, with
further refinement, may serve as a conceptual
substrate for the annotation types listed above:
1. DLF annotations, as suggested in Figure 3,
capture “(i) the applicable statutory and
regulatory requirements as a tree of authoritative
rule conditions (i.e., a “rule tree”) and (ii) the
chains of reasoning in the legal decision that
connect evidentiary assertions to the special
master’s findings of fact on those rule
conditions
        <xref ref-type="bibr" rid="ref22">(Walker et al., 2011)</xref>
        .”
2. Annotations in terms of presuppositional
information that “identifies entities (e.g., types
of vaccines or injuries), events (e.g., date of
vaccination or onset of symptoms) and
relations among them used in vaccine
decisions to state testimony about causation,
assessments of probative value, and findings of
fact.”
        <xref ref-type="bibr" rid="ref19 ref2 ref3">(Ashley and Walker, 2013a)</xref>
        .
3. Annotations of of argument patterns based
on: inference type (e.g., deductive or
statistical), evidence type (e.g., legal precedent,
policy, fact testimony), or type of weighing of
source credibility to resolve evidentiary
discrepancies (e.g., in terms of expert vs. expert
or of adequacy of explanation)
        <xref ref-type="bibr" rid="ref23">(Walker et al.,
2014)</xref>
        .
      </p>
      <p>
        If we succeed in designing a system of
coordinated legal annotation types and operationalizing
a UIMA annotation pipeline, we envision adding
a module to a full-text legal IR system. At
retrieval time it would extract semantic / pragmatic
legal information from the top n cases returned by
a traditional IR search and re-rank returned cases
to reflect the user’s diagrammatically specified
argument need. The module would also
summarize highly ranked cases and highlight
argumentrelated information
        <xref ref-type="bibr" rid="ref19 ref2 ref3">(Ashley and Walker, 2013a)</xref>
        .
Since the module processes the texts of cases
returned by the information retrieval system, no
special knowledge representation of the cases in the
IR system database is required; the knowledge
representation bottleneck will have been
circumvented.
7
      </p>
    </sec>
    <sec id="sec-10">
      <title>Conclusion</title>
      <p>According to Wittgenstein, meaning lies in the
way knowledge is used. Legal argument models
and argument schemes can specify roles for legal
propositions to play (and, interestingly, Stephen
Toulmin was a student of Wittgenstein.) Thus,
researchers can enable machines to search for and
use legal knowledge intelligently in order, among
other things, to improve legal information
retrieval.</p>
      <p>Although IBM Debater may identify
argument propositions (e.g., claims), legal argument
schemes could help it to address legal rules and
concepts, standards of proof, internal support and
attack relations, citation of statutory and case
authorities, attribution, and plausibility. Open
questions include the extent to which legal expert
knowledge will be needed in order to
operationalize argument schemes to extract arguments from
legal case texts.</p>
    </sec>
    <sec id="sec-11">
      <title>Acknowledgments</title>
      <p>My colleagues Vern Walker, Matthias Grabmair,
and Eric Nyberg make this work possible.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          <string-name>
            <given-names>K.</given-names>
            <surname>Ashley</surname>
          </string-name>
          and S. Bru¨ninghaus.
          <year>2009</year>
          .
          <article-title>Automatically classifying case texts and predicting outcomes</article-title>
          .
          <source>Artificial Intelligence and Law</source>
          , pages
          <fpage>125</fpage>
          -
          <lpage>165</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <string-name>
            <given-names>K.</given-names>
            <surname>Ashley</surname>
          </string-name>
          and
          <string-name>
            <given-names>V.</given-names>
            <surname>Walker</surname>
          </string-name>
          . 2013a.
          <article-title>From information retrieval (IR) to argument retrieval (AR) for legal cases: Report on a baseline study</article-title>
          . In K. Ashley, editor,
          <source>JURIX</source>
          , volume
          <volume>259</volume>
          <source>of Frontiers in Artificial Intelligence and Applications</source>
          , pages
          <fpage>29</fpage>
          -
          <lpage>38</lpage>
          . IOS Press.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          <string-name>
            <given-names>K.</given-names>
            <surname>Ashley</surname>
          </string-name>
          and
          <string-name>
            <given-names>V.</given-names>
            <surname>Walker</surname>
          </string-name>
          . 2013b.
          <article-title>Toward constructing evidence-based legal arguments using legal decision documents and machine learning</article-title>
          .
          <source>In Proc. 14th Int'l Conf. on Artificial Intelligence and Law</source>
          ,
          <source>ICAIL '13</source>
          , pages
          <fpage>176</fpage>
          -
          <lpage>180</lpage>
          , New York, NY, USA. ACM.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          <string-name>
            <given-names>S.</given-names>
            <surname>Beck</surname>
          </string-name>
          .
          <year>2014</year>
          .
          <article-title>Emerging technology shapes future of law</article-title>
          . http://www.americanlawyer. com/id=1202664266769/
          <string-name>
            <surname>EmergingTechnology-Shapes-</surname>
          </string-name>
          Future-of-Law. Accessed:
          <fpage>2014</fpage>
          -09-20.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          <string-name>
            <given-names>J.</given-names>
            <surname>Daniels</surname>
          </string-name>
          and
          <string-name>
            <given-names>E.</given-names>
            <surname>Rissland</surname>
          </string-name>
          .
          <year>1997</year>
          .
          <article-title>Finding legally relevant passages in case opinions</article-title>
          .
          <source>In ICAIL</source>
          , pages
          <fpage>39</fpage>
          -
          <lpage>46</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          <string-name>
            <given-names>J.</given-names>
            <surname>Dick</surname>
          </string-name>
          and
          <string-name>
            <given-names>G.</given-names>
            <surname>Hirst</surname>
          </string-name>
          .
          <year>1991</year>
          .
          <article-title>A case-based representation of legal text for conceptual retrieval</article-title>
          .
          <source>In Proceedings, Workshop on Language and Information Processing, American Society for Information Science</source>
          , pages
          <fpage>93</fpage>
          -
          <lpage>102</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          <string-name>
            <given-names>EA</given-names>
            <surname>Epstein</surname>
          </string-name>
          ,
          <article-title>MI Schor, BS Iyer, A. Lally, EW Brown, and</article-title>
          <string-name>
            <given-names>J.</given-names>
            <surname>Cwiklik</surname>
          </string-name>
          .
          <year>2012</year>
          .
          <article-title>Making Watson fast</article-title>
          .
          <source>IBM J. Res. and Dev</source>
          .,
          <volume>56</volume>
          (
          <issue>3</issue>
          .4):
          <fpage>15</fpage>
          -
          <lpage>1</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          <string-name>
            <given-names>J.</given-names>
            <surname>Fan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Kalyanpur</surname>
          </string-name>
          , DC Gondek, and
          <string-name>
            <given-names>DA</given-names>
            <surname>Ferrucci</surname>
          </string-name>
          .
          <year>2012</year>
          .
          <article-title>Automatic knowledge extraction from documents</article-title>
          .
          <source>IBM J. Res. and Dev</source>
          .,
          <volume>56</volume>
          (
          <issue>3</issue>
          .4):
          <fpage>5</fpage>
          -
          <lpage>1</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          <string-name>
            <given-names>V.</given-names>
            <surname>Feng</surname>
          </string-name>
          and
          <string-name>
            <given-names>G.</given-names>
            <surname>Hirst</surname>
          </string-name>
          .
          <year>2011</year>
          .
          <article-title>Classifying arguments by scheme</article-title>
          .
          <source>In Dekang Lin</source>
          , Yuji
          <string-name>
            <surname>Matsumoto</surname>
          </string-name>
          , and Rada Mihalcea, editors,
          <source>ACL</source>
          , pages
          <fpage>987</fpage>
          -
          <lpage>996</lpage>
          . The Association for Computer Linguistics.
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          2010.
          <article-title>Building Watson: An overview of the DeepQA project</article-title>
          .
          <source>AI Magazine</source>
          ,
          <volume>31</volume>
          (
          <issue>3</issue>
          ):
          <fpage>59</fpage>
          -
          <lpage>79</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          <string-name>
            <given-names>D.</given-names>
            <surname>Ferrucci</surname>
          </string-name>
          .
          <year>2012</year>
          .
          <article-title>Introduction to ”This is Watson”</article-title>
          .
          <source>IBM J. Res. and Dev</source>
          .,
          <volume>56</volume>
          (
          <issue>3</issue>
          .4):
          <fpage>1</fpage>
          -
          <lpage>1</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          <string-name>
            <given-names>T.</given-names>
            <surname>Gonc</surname>
          </string-name>
          <article-title>¸alves and</article-title>
          <string-name>
            <given-names>P.</given-names>
            <surname>Quaresma</surname>
          </string-name>
          .
          <year>2005</year>
          .
          <article-title>Is linguistic information relevant for the classification of legal texts?</article-title>
          <source>In Proc. 10th Int'l Conf. on AI and Law</source>
          ,
          <source>ICAIL '05</source>
          , pages
          <fpage>168</fpage>
          -
          <lpage>176</lpage>
          , NY, NY. ACM.
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          <string-name>
            <given-names>B.</given-names>
            <surname>Hachey</surname>
          </string-name>
          and
          <string-name>
            <given-names>C.</given-names>
            <surname>Grover</surname>
          </string-name>
          .
          <year>2006</year>
          .
          <article-title>Extractive summarisation of legal texts</article-title>
          .
          <source>Artificial Intelligence and Law</source>
          ,
          <volume>14</volume>
          (
          <issue>4</issue>
          ):
          <fpage>305</fpage>
          -
          <lpage>345</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          <string-name>
            <given-names>P.</given-names>
            <surname>Jackson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Al-Kofahi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Tyrrell</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Vachher</surname>
          </string-name>
          .
          <year>2003</year>
          .
          <article-title>Information extraction from case law and retrieval of prior cases</article-title>
          .
          <source>Artificial Intelligence</source>
          ,
          <volume>150</volume>
          (
          <issue>1- 2</issue>
          ):
          <fpage>239</fpage>
          -
          <lpage>290</lpage>
          , November.
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          <string-name>
            <given-names>L.T.</given-names>
            <surname>McCarty</surname>
          </string-name>
          .
          <year>2007</year>
          .
          <article-title>Deep semantic interpretations of legal texts</article-title>
          .
          <source>In Proc. 11th Int'l Conf. on AI and Law</source>
          ,
          <source>ICAIL '07</source>
          , pages
          <fpage>217</fpage>
          -
          <lpage>224</lpage>
          , NY, NY. ACM.
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          <string-name>
            <given-names>R.</given-names>
            <surname>Mochales</surname>
          </string-name>
          and
          <string-name>
            <given-names>M.-F.</given-names>
            <surname>Moens</surname>
          </string-name>
          .
          <year>2011</year>
          .
          <article-title>Argumentation mining</article-title>
          .
          <source>Artificial Intelligence and Law</source>
          ,
          <volume>19</volume>
          (
          <issue>1</issue>
          ):
          <fpage>1</fpage>
          -
          <lpage>22</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          <string-name>
            <given-names>H.</given-names>
            <surname>Prakken</surname>
          </string-name>
          .
          <year>2005</year>
          .
          <article-title>AI &amp; Law, logic and argument schemes</article-title>
          .
          <source>Argumentation</source>
          ,
          <volume>19</volume>
          (
          <issue>3</issue>
          ):
          <fpage>303</fpage>
          -
          <lpage>320</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          <string-name>
            <given-names>M.</given-names>
            <surname>Saravanan</surname>
          </string-name>
          and
          <string-name>
            <given-names>B.</given-names>
            <surname>Ravindran</surname>
          </string-name>
          .
          <year>2010</year>
          .
          <article-title>Identification of rhetorical roles for segmentation and summarization of a legal judgment</article-title>
          .
          <source>Artificial Intelligence and Law</source>
          ,
          <volume>18</volume>
          (
          <issue>1</issue>
          ):
          <fpage>45</fpage>
          -
          <lpage>76</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          <string-name>
            <given-names>A.</given-names>
            <surname>Sergeant</surname>
          </string-name>
          .
          <year>2013</year>
          .
          <article-title>Automatic argumentation extraction</article-title>
          . In et al. P. Cimiano, editor,
          <source>ESWC</source>
          , volume
          <volume>7882</volume>
          of Lecture Notes in Computer Science, pages
          <fpage>656</fpage>
          -
          <lpage>660</lpage>
          . Springer.
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          <string-name>
            <given-names>P.</given-names>
            <surname>Thompson</surname>
          </string-name>
          .
          <year>2001</year>
          .
          <article-title>Automatic categorization of case law</article-title>
          .
          <source>In Proc. 8th Int'l Conf. on AI and Law</source>
          ,
          <source>ICAIL '01</source>
          , pages
          <fpage>70</fpage>
          -
          <lpage>77</lpage>
          , NY, NY. ACM.
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          <string-name>
            <given-names>C.</given-names>
            <surname>Uyttendaele</surname>
          </string-name>
          ,
          <string-name>
            <surname>M.-F. Moens</surname>
            , and
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Dumortier</surname>
          </string-name>
          .
          <year>1998</year>
          .
          <article-title>Salomon: Automatic abstracting of legal cases for effective access to court decisions</article-title>
          .
          <source>Artificial Intelligence and Law</source>
          ,
          <volume>6</volume>
          (
          <issue>1</issue>
          ):
          <fpage>59</fpage>
          -
          <lpage>79</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          <string-name>
            <given-names>V.</given-names>
            <surname>Walker</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Carie</surname>
          </string-name>
          , C. DeWitt, and
          <string-name>
            <given-names>E.</given-names>
            <surname>Lesh</surname>
          </string-name>
          .
          <year>2011</year>
          .
          <article-title>A framework for the extraction and modeling of fact-finding reasoning from legal decisions: Lessons from the vaccine/injury project corpus</article-title>
          .
          <source>Artificial Intelligence and Law</source>
          , pages
          <fpage>291</fpage>
          -
          <lpage>331</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          <string-name>
            <given-names>V.</given-names>
            <surname>Walker</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Vazirova</surname>
          </string-name>
          , and
          <string-name>
            <given-names>C.</given-names>
            <surname>Sanford</surname>
          </string-name>
          .
          <year>2014</year>
          .
          <article-title>Annotating patterns of reasoning about medical theories of causation in vaccine cases: Toward a type system for arguments</article-title>
          .
          <source>In Proc. 1st Workshop on Argumentation Mining</source>
          ,
          <string-name>
            <surname>ACL</surname>
          </string-name>
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          <string-name>
            <given-names>A.</given-names>
            <surname>Wyner</surname>
          </string-name>
          and
          <string-name>
            <given-names>W.</given-names>
            <surname>Peters</surname>
          </string-name>
          .
          <year>2010</year>
          .
          <article-title>Lexical semantics and expert legal knowledge towards the identification of legal case factors</article-title>
          .
          <source>In Proc. 23d Conf. on Legal Knowledge and Information Systems: JURIX</source>
          <year>2010</year>
          , pages
          <fpage>127</fpage>
          -
          <lpage>136</lpage>
          , Amsterdam. IOS Press.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>