<!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>Answer Validation on English and Romanian Languages</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Adrian Iftene</string-name>
          <email>adiftene@info.uaic.ro</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Alexandra Balahur-Dobrescu</string-name>
          <email>abalahur@info.uaic.ro</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>UAIC: Faculty of Computer Science, “Alexandru Ioan Cuza” University</institution>
          ,
          <country country="RO">Romania</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>University of Alicante, Department of Software and Computing Systems</institution>
          ,
          <addr-line>Alicante</addr-line>
          ,
          <country country="ES">Spain</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The present article presents the steps involved in the transformation of the TE system that was used in the RTE3 competition in 2007 for the AVE 2008 exercise. We describe the rules followed in building the patterns for question transformation, the generation of the corresponding hypotheses and finally for answer ranking. We conclude by presenting an overview of the performance obtained by this approach and a critical analysis of the errors obtained. AVE1 (Answer Validation Exercise) is a task introduced in the QA@CLEF competition, with the aim of promoting the development and evaluation of subsystems validating the correctness of the answers given by QA systems. Participant systems receive a set of triplets (Question, Answer, and Supporting Text) and they must return a judgment of SELECTED, VALIDATED or REJECTED for each triplet. This year, for our second participation in the AVE competition, we improved the system used last year and, additionally introduced a question analysis part, which is specific to a question answering system. In this year's AVE competition we also participated with a system working in Romanian, using a Textual Entailment (TE) system working on Romanian. The latter is similar to the TE system working in English with which we participated in the RTE 3 competition in 2007 (Iftene, Balahur-Dobrescu, 2007b). Due to this reason, the present paper describes solely the AVE system working in English. The following sections present the new functionalities that have been added to our English TE system.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1 Introduction</title>
    </sec>
    <sec id="sec-2">
      <title>2 Textual Entailment System</title>
      <p>
        The main architecture of our Textual Entailment system remains the same
        <xref ref-type="bibr" rid="ref3 ref4">(Iftene, Balahur-Dobrescu, 2007a)</xref>
        .
The goal of the system is to transform the hypothesis making use of extensive semantic knowledge from
resources like DIRT, WordNet, Wikipedia, and database of acronyms. Additionally, we built a system to acquire
the extra Background Knowledge needed and applied complex grammar rules for rephrasing in English. Tools
used are LingPipe2 and MINIPAR3
        <xref ref-type="bibr" rid="ref5">(Lin, 1998)</xref>
        .
      </p>
      <p>
        Based on a tree edit distance algorithm
        <xref ref-type="bibr" rid="ref2">(Kouylekov and Magnini, 2005)</xref>
        , the main goal of our algorithm is to
map every entity in the dependency tree associated with the hypothesis to an entity in the dependency tree
associated with the text.
      </p>
      <p>For every mapping, we compute a local fitness value, which indicates the appropriateness between entities.
Based on this local fitness, further on an extended local fitness is computed and, eventually, using all partial
values, the global fitness is summed up. Two rules are also added for the global fitness calculation, namely:
•</p>
      <p>The Semantic Variability Rule – which is a rule regarding the negation of verbs, words that are
“stressing certainty (preserving it)” regarding the sense of the sentence and, on the other hand, words
that are “certainty diminishing” the sense of the sentence, negating it;
•</p>
      <p>The Rule for Named Entities - The rule is applied for named entities from the hypothesis which have
no correspondence in the text. If the word is marked as named entity by LingPipe, we try to use the
acronyms’ database or obtain information related to it from the background knowledge. In last year’s</p>
      <sec id="sec-2-1">
        <title>1 http://nlp.uned.es/QA/ave/</title>
        <p>2 http://www.alias-i.com/lingpipe/
3 http://www.cs.ualberta.ca/~lindek/minipar.htm
version of the TE system, in the event that even after these operations we cannot map the word from
the hypothesis to one word from the text, we set the value for the global fitness to 0.</p>
        <p>The main change from this year is regarding the Rule for Named Entities. There are cases where it is possible
for all pairs to have hypotheses with Named Entity problems. With the old rule, the global fitness for all these
pairs is set to 0, and it is thus impossible to select the best value (corresponding to the SELECTED answer).</p>
        <p>In the new rule, we compute the global fitness value for current pair, but we also mark the current pair as
having a “NE Problem”. Further on, we will see how this marking is used in ordering the answers and in the final
evaluation for the AVE task.</p>
        <p>Changing this rule helps our program in cases such as that of the question with id = “0054”:</p>
        <p>In which all justification snippets for answers contain the name “Mathieu Orfila”, but don’t contain the exact
article name “Traité des poisons”. From all possible answers, we select as correct the answer “1813”, with the
justification snippet:
Mathieu Orfila is considered to be the modern father of
toxicology, having given the subject its first formal treatment
in 1813 in Mathieu Orfila Trait des poisons, also called</p>
        <p>Toxicologie generate.</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3 Using the TE System in the AVE track</title>
      <p>The system architecture for this year is presented below:</p>
      <p>AVE
test data</p>
      <p>Question</p>
      <p>Answers
Justification
texts
pattern
building
text
building</p>
      <p>Patterns
hypothesis
building</p>
      <p>Text (T)</p>
      <p>Hypothesis</p>
      <p>(H)
Answer type
(AT)</p>
      <p>Expected Answer</p>
      <p>type (EAT)
if (AT = EAT) order
after global fitness</p>
      <p>AVE
Results1</p>
      <p>TE
System
order after
global fitness</p>
      <p>AVE
Results2
• From the system built for AVE 2007, we keep the following steps:</p>
      <p>We build a pattern with variables for every question according to the question type;
Using a pattern and all possible answers, we build a set of hypotheses for each of the questions: H1,
H2, H3 etc.;
We assign the justification snippet the role of text T and we run the TE system for all obtained pairs:
(T1, H1), (T2, H2), (T3, H3), etc.
• Additionally, we perform the next steps:</p>
      <p>Identify for the answers the Answer Type (AT);</p>
      <p>Identify for the questions the Expected Answer Type (EAT).</p>
      <sec id="sec-3-1">
        <title>Lastly, we submit two results for our system:</title>
        <p>1. In the first one we consider the correct answer for the current question the candidate from the
hypothesis for which we obtain the greatest global fitness;
2. In the second one, we consider the correct answer for the current question the candidate with AT equal
with EAT and for which we obtain the greatest global fitness.</p>
        <sec id="sec-3-1-1">
          <title>3.1 Pattern Building</title>
          <p>
            In order to use the TE system for ranking the possible answers in the AVE task, all these questions are first
transformed according to the algorithm presented in
            <xref ref-type="bibr" rid="ref1">(Bar-Haim et al., 2006)</xref>
            .
          </p>
          <p>For question 13 we have:
Question: What is the occupation of Richard Clayderman?</p>
        </sec>
      </sec>
      <sec id="sec-3-2">
        <title>Our program generates the following pattern:</title>
        <p>Pattern: The occupation of Richard Clayderman is JOB.</p>
        <p>where JOB is the variable in this case. We generate more specific patterns this year according to the following
answer types: City, Count, Country, Date, Job, Measure, Location, Person, Organization, Year and Other. Next
table presents the identified types of patterns:</p>
        <sec id="sec-3-2-1">
          <title>Pattern</title>
          <p>Organization</p>
        </sec>
      </sec>
      <sec id="sec-3-3">
        <title>Year</title>
      </sec>
      <sec id="sec-3-4">
        <title>Other 14 6 21</title>
      </sec>
      <sec id="sec-3-5">
        <title>What is the political party of Tony Blair?</title>
        <sec id="sec-3-5-1">
          <title>ORGANIZATION is the</title>
          <p>political party of Tony Blair.</p>
        </sec>
      </sec>
      <sec id="sec-3-6">
        <title>In what year did Emer</title>
        <p>son Lake&amp;Palmer form?</p>
      </sec>
      <sec id="sec-3-7">
        <title>Emerson Lake&amp;Palmer was</title>
        <p>form in YEAR.</p>
      </sec>
      <sec id="sec-3-8">
        <title>In Japanese, what is</title>
        <p>"bungo"?
"bungo" is OTHER.</p>
        <p>Following the building of the pattern, we proceed to constructing the corresponding hypotheses. A special case
is for DEFINITION questions, when we didn’t build any pattern (in this case only the answer will be the
hypothesis).</p>
        <sec id="sec-3-8-1">
          <title>3.2 Hypothesis building</title>
          <p>Using the pattern building mechanism above and the answers provided within the AVE data, we built the
corresponding hypotheses. For example, for question 27, we build, according to the answers from the English test
data (“a_str” tags), the following hypotheses:</p>
          <p>H13_1: The occupation of Richard Clayderman is Number.</p>
          <p>H13_2: The occupation of Richard Clayderman is teacher
Qualifications.</p>
          <p>H13_3: The occupation of Richard Clayderman is ways.</p>
          <p>H13_8: The occupation of Richard Clayderman is pianist.</p>
          <p>H13_11: The occupation of Richard Clayderman is artist.</p>
          <p>H13_12: The occupation of Richard Clayderman is Composer.</p>
          <p>H13_13: The occupation of Richard Clayderman is teachers.</p>
          <p>For each of these hypotheses, we consider as having the role of text T the corresponding justification text
(content of the “t_str” tag).</p>
        </sec>
        <sec id="sec-3-8-2">
          <title>3.3 Global Fitness Calculation</title>
          <p>We consider the pairs built above as input for our Textual Entailment system. After running the TE system, the
global fitness values and the values with marked “NE Problems” for these pairs are the following:
Pair</p>
        </sec>
        <sec id="sec-3-8-3">
          <title>3.4 Answers Type and Expected Answer Type Identification</title>
          <p>The aim in performing this step is to eliminate the cases in which there are differences between these values.
For example, in the case of question 13, since the expected answer type is JOB, it is normal to try to identify the
correct answer in the sub-set of answers of type JOB.</p>
          <p>The patterns used in the identification of the expected answer type (EAT) are similar to the patterns used in
3.1. For the identification of the answer type (AT), we use GATE4 for the following types: Job, City, Country,
Location, Person, Organization and we build specific patterns in order to identify the following types: Date,
Measure, and Count. When an answer cannot be classified with GATE or with our patterns, it is considered with
type Other. For question number 13, we have:</p>
          <p>Pair</p>
          <p>On last column is the matching score between EAT and AT. In order to compute this value, we use a set of
rules. The most important rules are:</p>
        </sec>
        <sec id="sec-3-8-4">
          <title>3.4 Answers classification</title>
          <p>We submit two runs on each of the languages (English and Romanian) according to the use or not of some
system components. The systems are similar and only the external resources used by the TE system or by GATE are
language-specific.</p>
          <p>First run: is based on TE System output. The answers for which we have NE problems are considered as
REJECTED (for question 13, using table 4, we can deduce that answers 1, 2, 3 and 13 are REJECTED). Answers</p>
        </sec>
      </sec>
      <sec id="sec-3-9">
        <title>4 http://www.gate.ac.uk/</title>
        <p>without NE problems are considered as VALIDATED (answers 8, 11, 12) and the answer with the highest global
fitness is considered as SELECTED (answer 8). If all answers contain NE problems, then all answers are
considered REJECTED, except the answer with highest global fitness, which will be considered SELECTED.</p>
        <p>Second run: in addition to the first run, we add the comparison between EAT and AT. In the cases where we
have NE Problems, the answers are considered as REJECTED as well, and we also take into consideration if the
matching score between EAT and AT is 0 (incompatible types). Of the remaining answers, if the matching score
is not 0, then all answers are VALIDATED. For the identification of the SELECTED answer, we select the
answers with the highest matching score (8, 11, 12) and the highest global fitness. In this case, the results are the
same.</p>
        <sec id="sec-3-9-1">
          <title>3.5 Results</title>
        </sec>
      </sec>
      <sec id="sec-3-10">
        <title>Our AVE systems have the following results:</title>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4 Conclusions</title>
      <p>Last year, we showed how the TE system used in the RTE3 competition can successfully be used as part of the
AVE system, resulting in improved ranking between the possible answers, especially in the case of questions with
answers of type Person, Location, Date and Organization. This year, changing some of the rules employed in the
Textual Entailment system and adding the question and answer type classification and matching component, we
showed how we improved, on the one hand, the correct classification of the answers, and on the other hand, the
validation of more answers.</p>
      <p>One of the main problems encountered was the class of UNKNOWN answers types, which our system does
not identify. In order to detect these cases, a three way classification of the answers, such as that proposed in the
RTE 3 pilot task is intended to be used in the future.</p>
      <p>The rule regarding the presence of NEs remains of great importance, identifying the correct cases. However, in
the cases where the NER or NEC is not correctly performed, the system fails. Moreover, this rule is not enough
to identify the entire class of REJECTED answers, as shown in table 8. In order to better identify these situations,
additional rules must still be explored in order to further improve the system.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          <string-name>
            <surname>Bar-Haim</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dagan</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dolan</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ferro</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Giampiccolo</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Magnini</surname>
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Szpektor</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          <year>2006</year>
          .
          <article-title>The Second PASCAL Recognising Textual Entailment Challenge</article-title>
          .
          <source>In Proceedings of the Second PASCAL Challenges Workshop on Recognizing Textual Entailment. Venice. Italy.</source>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <string-name>
            <surname>Kouylekov</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Magnini</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          <year>2005</year>
          .
          <article-title>Recognizing Textual Entailment with Tree Edit Distance Algorithms</article-title>
          .
          <source>In Proceedings of the First Challenge Workshop Recognising Textual Entailment, Pages 17-20</source>
          ,
          <fpage>25</fpage>
          -
          <lpage>28</lpage>
          April,
          <year>2005</year>
          , Southampton, U.K.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          <string-name>
            <surname>Iftene</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Balahur-Dobrescu</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <year>2007a</year>
          .
          <article-title>Hypothesis Transformation and Semantic Variability Rules Used in Recognizing Textual Entailment</article-title>
          .
          <source>In Proceedings of the ACL-PASCAL Workshop on Textual Entailment and Paraphrasing. Pages 125-130</source>
          .
          <fpage>28</fpage>
          -29 June, Prague, Czech Republic.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          <string-name>
            <surname>Iftene</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Balahur-Dobrescu</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <year>2007b</year>
          .
          <article-title>Improving a QA System for Romanian Using Textual Entailment</article-title>
          .
          <source>In Proceedings of RANLP workshop “A Common Natural Language Processing Paradigm For Balkan Languages”. Pages 7-14, September</source>
          <volume>26</volume>
          ,
          <string-name>
            <surname>Borovets</surname>
          </string-name>
          , Bulgaria.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          <string-name>
            <surname>Lin</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <year>1998</year>
          .
          <article-title>Dependency-based Evaluation of MINIPAR</article-title>
          .
          <source>In Workshop on the Evaluation of Parsing Systems</source>
          , Granada, Spain, May.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>