<!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>LIMSI-CNRS@CLEF 2015: Tree Edit Beam Search for Multiple Choice Question Answering</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Martin Gleize</string-name>
          <email>gleize@limsi.fr</email>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Brigitte Grau</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>ENSIIE</institution>
          ,
          <addr-line>Evry</addr-line>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>LIMSI-CNRS</institution>
          ,
          <addr-line>Rue John von Neumann, 91405 Orsay CEDEX</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Universite Paris-Sud</institution>
          ,
          <addr-line>Orsay</addr-line>
        </aff>
      </contrib-group>
      <abstract>
        <p>This paper describes our participation to the Entrance Exams Task of CLEF 2015's Question Answering Track. The goal is to answer multiple-choice questions on short texts. Our system rst retrieves passages relevant to the question, through lexical expansion involving WordNet and word vectors. Then a tree edit model is used on graph representations of the passages and answer choices to extract edit sequences. Finally, features are computed from those edit sequences and used in various machine-learned models to take the nal decision. We submitted several runs in the task, one of which yielding a c@1 of 0.36, which makes our team the second best on the task.</p>
      </abstract>
      <kwd-group>
        <kwd>Question Answering</kwd>
        <kwd>Passage Retrieval</kwd>
        <kwd>Textual Entailment</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>in Figure 1. Its pipeline is composed of mainly ve modules: preprocessing,
passage retrieval, graph enrichment, beam search with tree edit model and nal
classi ers for validation/invalidation. The remaining of this section is dedicated
to the detailed description of those modules.</p>
      <sec id="sec-1-1">
        <title>Document / Question / Answer choice</title>
      </sec>
      <sec id="sec-1-2">
        <title>Preprocessing</title>
      </sec>
      <sec id="sec-1-3">
        <title>Passage retrieval</title>
      </sec>
      <sec id="sec-1-4">
        <title>Graph enrichment</title>
      </sec>
      <sec id="sec-1-5">
        <title>Tree edit beam search</title>
      </sec>
      <sec id="sec-1-6">
        <title>Machine-learned classifier</title>
      </sec>
      <sec id="sec-1-7">
        <title>Validation score / Invalidation score</title>
        <p>
          We use Stanford CoreNLP as the main Natural Language annotation tool. Each
sentence from the document, questions or answer choices is tagged with
PartOf-Speech [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ] and syntactically parsed [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ]. In addition, a coreference resolution
system [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ] is applied on the whole document as well as question-answer pairs. We
add to this coreference resolution process manual rules derived from the data,
like replacing rst person pronouns in non-dialogue context with \the author"
or \the writer", depending on which is used in the questions. Named Entity
Recognition was not used, due to not being very helpful in past editions of
Entrance Exams. NER is very important to factoid QA, because it produces
annotations which correspond roughly to the expected type of answer, but on
complex multiple-choice questions which rarely use entities as an answer type,
it is intuitively less crucial.
2.2
        </p>
        <sec id="sec-1-7-1">
          <title>Passage Retrieval</title>
          <p>The passage retrieval module aims at extracting relevant short snippets from
the document to pass to the more computationally expensive modules further
down the pipeline. Words of the question and the answer choice act as the query.
However, it is very rare that words of the question exactly appear in the relevant
passage of the document, so we have to use some form of query expansion.
We enrich the lemmas with coreference information, WordNet relations
(synonyms, antonyms, hypernyms, hyponyms), and weigh the words by the IDF
score of the original word in the document.</p>
          <p>
            If the words of the query are not found using the previous expansion methods,
we use a vector-based representation of words to compute a similarity measure.
Word vectors are those found in [
            <xref ref-type="bibr" rid="ref3">3</xref>
            ]. To each word, we assign a vector of 50
values. [
            <xref ref-type="bibr" rid="ref3">3</xref>
            ]'s resource actually provides multiple vectors for each word, to account
more accurately for polysemy, so we use the same window-based disambiguation
method as the author to compute the right one. We then pair the query word
vectors with the document word vectors with the highest cosine similarity. We
also take into account bigram vectors, by summing 2 vectors, which means that
we can e ectively handle 1-to-2, 2-to-1 and 2-to-2 scored alignments.
Passages are ranked according to the scoring function de ned by Equation 1 and
are then naturally extended to the full sequence of sentences they span.
score(passage) =
#matchedW ords
#queryW ords
i=1
n 1
X score(wi) + score(wi+1)
dist(i; i + 1)2
(1)
We take into account the potential absence of query words by multiplying the
passage score by the fraction of query words the passage contains. Each wi 2
fw1; :::; wng a document word matching a query word is given a simple alignment
score (1 if they have same lemmas, 0.9 if they are WordNet synonyms, 0.8 if
they are in another WordNet relation, and their word vector cosine similarity
otherwise), weighted with the IDF of the word, and the formula is normalized
by the square of the distance between the words in the sentence.
Overall, this passage retrieval method retrieves a lot of short passages, most of
which will overlap or won't be correct, but the beam search which uses them is
designed to handle numerous source passages.
2.3
          </p>
        </sec>
        <sec id="sec-1-7-2">
          <title>Graph Enrichment</title>
          <p>
            The passages were syntactically parsed with Stanford CoreNLP to obtain the
initial dependency graphs. We fuse those graphs together by linking their roots
with a followed-by arc which materializes in the single remaining graph that a
sentence is followed by another in the passage. Then we use ConceptNet [
            <xref ref-type="bibr" rid="ref5">5</xref>
            ] to
enrich the graph.
          </p>
          <p>ConceptNet is a semantic triplet base containing relations about common-knowledge
of the world, designed to be used especially for machine understanding of text
written by people. It is built from nodes representing words or short phrases of
natural language, and labeled relationships between them (the nodes are called
"concepts" for tradition, but they'd be better known as "terms".) For
example, ConceptNet contains everyday basic knowledge, like MotivatedByGoal(learn,
knowledge): you would learn because you want knowledge. It also contains
cultural knowledge, like UsedFor(saxophone, jazz): a saxophone is used for jazz.
Our assumption is that understanding the documents in the Entrance exams
corpus requires a lot of human common-sense, easily acquired by human readers
of that level, but di cult to grasp for computers. So we want to enrich the text
with relations which attempt to ll that gap.</p>
          <p>Concepts from ConceptNet are mainly single words, like \saxophone" or \jazz",
so they are easy to link to our original graph. However, it is not easy to integrate
relations to our graph, because they have labels that are potentially composed
of several words, like UsedFor or MotivatedByGoal. We could split those labels
into words and use those in the graph, but we preferred attaching to the
original graph the parse tree of the surfaceText element of the relations. Surface
texts are the original natural language text that expressed the statement, like
\a saxophone is used for jazz". We attach the parse tree of these sentences to
any concept whose head word is in the original graph. We only retrieve from
ConceptNet relations that are indicative of an entailment relation of any kind,
namely: IsA, PartOf, MemberOf, UsedFor, CapableOf, Causes, HasPrerequisite,
MotivatedByGoal, Desires.
2.4</p>
        </sec>
        <sec id="sec-1-7-3">
          <title>Tree edit beam search</title>
          <p>Tree edit model Our goal is to characterize a sequence of transformations
applied to the passage to obtain the answer choice. Those transformations a ect
the graph built in the previous section, which is made of parse trees, and the
transformations will be called edits, hence a tree edit model. Basically, we apply
di erent edits iteratively to the tree, modifying it each time, so that the edited
tree is closer to the tree of the answer choice. When we nd an edit sequence to
turn the passage into the answer choice, we look at the nature of edits that were
e ectively applied, and if they are elements of proof that the passage is indeed
close to the answer choice, or if it is too far to conclude anything. This will be
done in the subsequent sections.</p>
          <p>Table 1 presents the supported edit operations. Figure 2 presents an example of
successive applications of three of them.</p>
          <p>Beam search The main problem is that there are many choices to make when
applying an edit. Which edit to choose? Where to apply changes in the tree?
What new elements must be added? What to do next? Any of these choices is
an easy source of error, so rather than picking one each time and hoping to nd
Edit operation Description
Delete(d: Tree) Delete the node d and replace it with its children.
Insert(i: Word, p: Tree) Insert the word i under its new parent p.
Rename(t: Tree, w: Word) Replace the word attached to the node t with w.
Move(m: Tree, op: Tree, np: Tree) Move the subtree m from under op to under np.
the right edit sequence, we apply a lot of the possible edits, and explore only the
most promising using a satisfyingly good heuristic.</p>
          <p>Beam search is an optimization of best- rst search that reduces its memory
requirements. It uses breadth- rst search to build its search space. At each step
of the search, we generate all possible edits of the trees at the current step, sorting
them in increasing order of heuristic cost de ned below. However, we only store
a predetermined number of best trees at each level, called the beam width. Only
those trees are edited next and the rest is discarded. This method allows to
netune via the beam width the probability to nd useful edit sequences and the
memory and time costs.</p>
          <p>
            Partial Tree Kernel as a heuristic We need a heuristic measure of how far
a tree at the current step is from the target tree (the dependency tree of an
answer choice). We implement the Partial Tree Kernel de ned in [
            <xref ref-type="bibr" rid="ref6">6</xref>
            ] to compute
the similarity between the current tree and the target tree. As a tree kernel, it
classically computes the number of common subtrees between 2 trees, but this
particular version of the tree kernel is adapted to n-ary trees, which is what
we have in dependency structures. The kernel computation is normalized with
K~ (x; y) = pK(xK;x()xp;yK)(y;y) , for K the kernel and x; y the trees.
          </p>
          <p>Algorithm At the start of the algorithm, the working set consists solely of
the enriched dependency graphs of all the retrieved passages. The target tree is
the answer choice (or the question plus the answer choice when the answer is
an end to the question sentence as can be the case in the CLEF dataset). In
our experiments, we keep at most 10 passages in the retrieval step. Then, every
possible relevant edit operation is applied to each passage. Inserts and renames
can only add a node that is present in the target tree. Moves can only move a
node under a parent so that the link parent ! child is present in the target tree.
Those edited trees are added to the working set, and the partial tree kernel with
the target tree is computed for all of them. The working set is then ltered to
only the top 50 trees with the best kernel score (50 is our beam width) and the
algorithm can now start again with the application of the edit operations on the
new working set.</p>
          <p>It stops when 10 di erent edit sequences have been found (some ltering is done
to ensure that we do not obtain mere variations of the rst sequence found), or
after 200 edit steps, whichever comes rst.
2.5</p>
        </sec>
        <sec id="sec-1-7-4">
          <title>Feature extraction</title>
          <p>The goal is to classify an edit sequence with two di erent machine-learned
classi ers, one to decide if the related answer choice is validated, and one to decide
if it is invalidated. The design of features is thus primordial. In practice, we
will use the same features and the same machine learning algorithm for the two
classi ers, so the only di erence will be the training data, discussed in the next
section.</p>
          <p>Most features are counts of speci c edit unigrams or bigrams in the edit
sequence, and are summarized in Table 2. Pre-processing informations that were
not used in the beam search are used at this point, like dependency relations in
the parse tree, coreferences, and whether what we edit was part of the
ConceptNet additions or can be linked in WordNet.
3</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>Experiments and results</title>
      <p>3.1</p>
      <sec id="sec-2-1">
        <title>CLEF 2015 QA Track: Entrance Exams data and evaluation</title>
        <p>Our data consist of the trial and test sets at CLEF 2015 Question Answering
Track, Task 2: Entrance Exams. The trial data is composed of the test sets at
CLEF 2013 and 2014, each containing a series of 12 texts, and for each of them, 4
to 6 multiple-choice questions to answer, for about 120 questions in total. In the
2015 test set, there are 19 documents, and a total of 89 questions. There are 4
answer choices possible for each of the questions. This corpus has been extracted
from the Tokyo University Entrance Exam in English as a foreign language.
Systems are evaluated according to their c@1, de ned in equation 2.
n1 (nR + nU nnR )
(2)
with n the total number of questions, nR the number of correctly answered
questions, nU the number of unanswered questions.
moveTotal
moveVerb
...
moveConceptNet
moveMoreThan2Nodes
All bigram combinations of the above Number of pairs of the successive given edits in
the sequence
dependencyEditSequence Number of pairs of successive edits applied to
2 nodes in a dependency relation
originalTotal Fraction of the original words, verbs, nouns,
originalVerb proper nouns, that was not edited in the
se... quence</p>
        <p>Description
Total number of edits in the sequence
Number of total delete edits, edits which delete
a verb, a noun, a proper noun, a subject
(indicated by the subj Stanford dependencies), an
object, the root of the tree, a negation
(indicated by the neg dependency), and something
added to the graph through ConceptNet
Analogous to the above, for insert edits
Analogous to the above, for rename edits +
edits which rename a word into its synonym in
WordNet, or into its antonym in WordNet, or
into a hypernym/hyponym in Wordnet, edits
which rename a word into another with strong
word vector similarity (above a threshold,
de</p>
        <p>ned empirically), edits which rename a
pronoun into its referent according to the Stanford
coreference resolution, and edits which rename
a pronoun into some other referent
Analogous to the above, for move edits + edits
which move more than 2 nodes
3.2</p>
      </sec>
      <sec id="sec-2-2">
        <title>Learning classi ers</title>
        <p>
          The classi er pair, for validation and invalidation, uses the feature set de ned in
the previous section. We experimented with two models, logistic regression and
random forest, both implemented in Weka [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ], and results are presented in the
next subsection. We focus here on how we built our training data.
What we want to avoid is trying to learn how to transform any random text
snippet in the document into any random answer choice, because it serves no
purpose. Indeed, as readers, we cannot validate the right answer choice by
looking at a couple of arbitrary sentences in the text, nor can we invalidate a wrong
answer choice if the passage we are reading is not even related to the question.
Thus, we annotate the relevant passages in the training data manually, and our
algorithm runs on them, without a passage retrieval phase. A relevant passage
is roughly the su cient text snippet which expresses both the question and the
elements of the answer choice. Of course, sometimes the answer choice is not
exactly expressed by the passage, as commonly happens for wrong answer choices,
and sometimes, albeit rarely, the answer choice is not even expressed at all in
the document. Two answer choices to the same question can share a relevant
passage, as we annotate complete sentences.
        </p>
        <p>We create the learning (passage, answer choice) pairs by annotating them
following the semantics described in Figure 3. In this gure, RP stands for right
passage, RA for right answer, WA for any wrong answer, WAx for the wrong
answer choice x, WPx for the passage expressing it, OP for any other passage
than the one expressing the paired answer choice. To summarize, the only time
we can either validate or invalidate are when we operate on passages relevant
to some answer choice: we annotate as validated only if we have both the right
passage and the right answer, and invalidated if we have a wrong answer choice
with either the passage which expresses it in the document or the right passage.
This follows the intuition that as readers, given a question, a passage and an
answer choice, we can probably tell if the provided passage is self-su cient in
expressing the right answer to the question or if there is a mismatch between an
answer choice and the passage in the text it refers to.</p>
        <p>Then the edit sequences for this data are computed, their features are extracted,
and sequences for both classi ers are labeled using the aforementioned
semantics. Implicitly, as this is not visible in Figure 3, if an edit sequence is labeled 1
(valide/invalidate) for one classi er, it is labeled 0 for the other. The thin dashed
arrows simply symbolize that the label is 0 for both classi ers.</p>
        <p>For the test run, the algorithm runs on the test data, and the answer is
chosen based on the regression numbers output by the two classi ers. First, for
each answer choice, the edit sequence with the highest max (validationScore,
invalidationScore) is selected. Ideally we want an edit sequence which is
characteristic of either a high con dence validation, or a high con dence invalidation,
so that we may classify the answer choice con dently as either correct or
incorrect in the next step. Then, the answer choice whose selected sequence has the
highest validationScore invalidationScore is nally picked: we want in
RP / WA
WPx / RA
WPx / WAx
WPx / WAy
OP / RA
OP / WA</p>
        <p>Validated
Cannot judge
Invalidated
1
0
1</p>
        <p>Validation
Classifier
Invalidation</p>
        <p>Classifier
correctly classi ed answer choices as much separation between their validation
and invalidation scores as possible. If they have a similar validation and
invalidation score, the system just ends up guessing. We acknowledge that this is a
very basic decision process and address this point more in detail in Section 3.5.
3.3</p>
      </sec>
      <sec id="sec-2-3">
        <title>Results</title>
        <p>In this section, we report the results of our two learning models on the testing
set of questions. Table 3 presents those results. A c@1 of 0.36 gave us the second
place among teams which participated in the task.</p>
        <p>Random forest Logistic regression
89 89
57 61
0.360 0.314</p>
        <p>8 4
0.360
0.314</p>
        <p>The random forest model performed better on the test run, which con rms
what we expected during development.
3.4</p>
      </sec>
      <sec id="sec-2-4">
        <title>Error analysis</title>
        <p>Qualitative analysis A pertinent qualitative analysis is always delicate to do
for machine learning systems with such low performances. It is indeed always
possible to draw examples that look like the system is obviously supposed to
correctly handle but end up as errors. Conversely, it is always possible to nd a
complex instance on which the system somewhat miraculously worked (i.e. made
a lucky guess).</p>
        <p>Nevertheless, we rst report some of the simple errors that our system made.
In the following passage/question pair, our system got lured by answer 3,
closest in surface form to the relevant passage. ConceptNet does not link "held" to
"trapped", and "its original nature" from the correct answer could not be linked
to anything in the passage (it is however found further in the text).
Several years ago, certain scientists developed a way of investigating the nature
of the atmosphere of the past by studying air caught in the ice around the
North or South Pole. According to their theory, when snow falls, air is trapped
between the snow akes. The snow turns to ice with the air still inside.
Certain scientists claimed that
1) atmospheric gases increase the yearly amount of snow
2) falling snow akes change the chemical balance of the air
3) the action of atmospheric gases causes snow to turn into ice
4) the air held between snow akes keeps its original nature (correct)
In the following passage/question pair, our system picked the answer choice 3.
It would have been easy to pick the correct answer 1 if "wrong" could have been
linked to "mistake", but in ConceptNet, this is a RelatedTo relation, which we
did not consider. We realize that there is actually a lot of information in those
RelatedTo relations, and ideally our system should handle them, but we decided
in the design phase to remove them because they are not semantically precise.
Everyone stared. That was embarrassing enough, but it was worse when I
nished my co ee and got ready to leave. My face went red - as red as his hair
- when I realized I'd made a mistake.</p>
        <p>The woman's face turned red
1) because she realized that she had been quite wrong about the boy (correct)
2) because she realized that the boy was poor and hungry
3) because she saw everyone staring at her
4) because she hated being shouted at
In both those cases, a more precise characterization of correct passages would
have been useful, because in the rst case, our answer choice skips over the
sentence which contains the correct answer, and in the second case, the sentence
containing our answer choice appears way before the sentence containing both
question and correct answer.</p>
        <p>Finally we report an example of correctly answered question through mostly
invalidation. In the following passage/question pair, our system frankly
invalidated answer choice 1 (due to the added negation) and answer choice 4 (due to
the rst sentence of the passage saying the opposite). Then, answer choice 2 had
edit sequences which hinted at both validation and invalidation, so it was still a
risky pick (but with slightly more invalidation). In the end, the remaining answer
choice (3), for which the system found neither validation nor invalidation, was
correctly picked by default.</p>
        <p>Kate was an energetic woman who expected people always to be doing
something, and she found plenty of jobs for Fred to do. This made him feel part of
the household, but now he really wanted to be able to sit and re ect on the
events of his life. If he had continued to live alone, he would have had the time
to do this to his heart's content. One afternoon he felt he simply had to get
away from the house. "I'm going for a walk," he said, closing the door behind
him. Leaving the town, he walked across the elds and followed a slow-moving
stream toward the hills. After a while he came to a pool in the stream under
some trees. Here, he thought, was a place he could come to when he needed to
re ect on the past. Although the stream seemed unlikely to have any sh, he
would simply tell Kate he had found a place to go shing. When he mentioned
the stream that night, his son-in-law, Jim, said in disbelief, "There aren't any
sh there. That stream runs dry half the summer."
Why did Fred tell Kate that he had found a place to go shing?
1) He didn't feel part of the household with Kate and Jim.
2) He enjoyed shing very much and was glad to be able to do it again.
3) He wanted a way to leave the house without hurting Kate's feelings.
4) He was bored in the house because there were few things to do.
Quantitative analysis The general trend was that our system performed
better when edit sequences remained short, with over 40% accuracy when the chosen
edit sequences are shorter than 6 edits (on average on all the answer choices).
We considered this was still not signi cant enough of an advantage to choose
not to answer questions based on a length threshold of edit sequences.
3.5</p>
      </sec>
      <sec id="sec-2-5">
        <title>Future work</title>
        <p>We did not take advantage of the possibility to choose not to answer a question.
In our experience, every missed answer adds variance when running on the test
set (we are evaluated on even fewer questions, when there are not many to begin
with), so we did not prioritize exploiting this feature of the evaluation. However,
we believe our learning method has the potential to handle it. In future works,
it would be interesting to design a meta-classi er working on the output of the
two current classi ers.</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Conclusion</title>
      <p>Our system has been developed to answer multiple-choice questions. We extract
features from edit sequences obtained from our tree edit beam search method,
and learn two classi ers for validation and invalidation of answer choices. In the
CLEF 2015 evaluation campaign, Question Answering track, Entrance Exams
task, our best submitted run obtained the second performance among teams.
In further works, we plan to improve our graph enrichment method, which seems
to be a promising avenue. We are considering adding paraphrases to the graph.
Moreover, we plan to develop a meta-classi er dealing with the nal decision,
based on the individual validation/invalidation scores per answer choice, instead
of relying on manually crafted rules.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Gleize</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Grau</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>A hierarchical taxonomy for classifying hardness of inference tasks</article-title>
          . In: Chair),
          <string-name>
            <given-names>N.C.C.</given-names>
            ,
            <surname>Choukri</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            ,
            <surname>Declerck</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            ,
            <surname>Loftsson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            ,
            <surname>Maegaard</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            ,
            <surname>Mariani</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            ,
            <surname>Moreno</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Odijk</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            ,
            <surname>Piperidis</surname>
          </string-name>
          , S. (eds.)
          <source>Proceedings of the Ninth International Conference on Language Resources and Evaluation (LREC'14)</source>
          .
          <source>European Language Resources Association (ELRA)</source>
          , Reykjavik, Iceland (may
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Hall</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Frank</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Holmes</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pfahringer</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reutemann</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Witten</surname>
            ,
            <given-names>I.H.</given-names>
          </string-name>
          :
          <article-title>The weka data mining software: an update</article-title>
          .
          <source>ACM SIGKDD explorations newsletter 11(1)</source>
          ,
          <volume>10</volume>
          {
          <fpage>18</fpage>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Huang</surname>
            ,
            <given-names>E.H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Socher</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Manning</surname>
            ,
            <given-names>C.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ng</surname>
            ,
            <given-names>A.Y.</given-names>
          </string-name>
          :
          <article-title>Improving word representations via global context and multiple word prototypes</article-title>
          . In:
          <article-title>Proceedings of the 50th Annual Meeting of the Association for Computational Linguistics: Long Papers-Volume 1</article-title>
          . pp.
          <volume>873</volume>
          {
          <fpage>882</fpage>
          .
          <article-title>Association for Computational Linguistics (</article-title>
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Klein</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Manning</surname>
          </string-name>
          , C.D.:
          <article-title>Accurate unlexicalized parsing</article-title>
          .
          <source>In: Proceedings of the 41st Annual Meeting on Association for Computational Linguistics-Volume</source>
          <volume>1</volume>
          . pp.
          <volume>423</volume>
          {
          <fpage>430</fpage>
          .
          <article-title>Association for Computational Linguistics (</article-title>
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Liu</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Singh</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Conceptneta practical commonsense reasoning tool-kit</article-title>
          .
          <source>BT technology journal 22(4)</source>
          ,
          <volume>211</volume>
          {
          <fpage>226</fpage>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Moschitti</surname>
          </string-name>
          , A.:
          <article-title>E cient convolution kernels for dependency and constituent syntactic trees</article-title>
          .
          <source>In: Machine Learning: ECML</source>
          <year>2006</year>
          , pp.
          <volume>318</volume>
          {
          <fpage>329</fpage>
          . Springer (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Recasens</surname>
          </string-name>
          , M., de Marne e, M.C.,
          <string-name>
            <surname>Potts</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>The life and death of discourse entities: Identifying singleton mentions</article-title>
          .
          <source>In: Proceedings of the 2013 Conference of the North American Chapter of the Association for Computational Linguistics: Human Language Technologies</source>
          . pp.
          <volume>627</volume>
          {
          <issue>633</issue>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Sutcli</surname>
            <given-names>e</given-names>
          </string-name>
          , R., Pen~as,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Hovy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            ,
            <surname>Forner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            ,
            <surname>Rodrigo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Forascu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            ,
            <surname>Benajiba</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            ,
            <surname>Osenova</surname>
          </string-name>
          ,
          <string-name>
            <surname>P.</surname>
          </string-name>
          :
          <article-title>Overview of qa4mre main task at clef 2013</article-title>
          . Working Notes, CLEF (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Toutanova</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Klein</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Manning</surname>
            ,
            <given-names>C.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Singer</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          :
          <article-title>Feature-rich part-of-speech tagging with a cyclic dependency network</article-title>
          .
          <source>In: Proceedings of the 2003 Conference of the North American Chapter of the Association for Computational Linguistics on Human Language Technology-Volume 1</source>
          . pp.
          <volume>173</volume>
          {
          <fpage>180</fpage>
          .
          <article-title>Association for Computational Linguistics (</article-title>
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>