<!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>Cross Lingual Question Answering using QRISTAL for CLEF 2005</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Dominique Laurent</string-name>
          <email>dlaurent@synapse-fr.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Patrick Séguéla</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Sophie Nègre</string-name>
          <email>sophie.negre@synapse-fr.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Synapse Développement 33 rue Maynard</institution>
          ,
          <addr-line>31000 Toulouse</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2005</year>
      </pub-date>
      <abstract>
        <p>QRISTAL [8] is a question answering system making intensive use of natural language processing both for indexing documents and extracting answers. It recently ranked first in the EQueR evaluation campaign (Evalda, Technolangue [3]). This article proposes a functional description of the system. Then, it presents our results for the CLEF 2005 campaign and a critical description of the system. QRISTAL is possibly the first Question Answering system available on the consumer market. That fact generates drastic constraints and explains the technical choices we detail here.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>For French, our system is based on the Cordial technology. It massively uses NLP tools, such as syntactic
analysis, semantic disambiguation, anaphora resolution, metaphor detection, handling of converses, named
entities extraction as well as conceptual and domain recognition. As the product is being marketed, it required a
constant optimization of the various modules so that the software remains extremely fast. Users are now
accustomed to obtain something that looks like an answer within a very short time, not exceeding three seconds.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Architecture</title>
      <sec id="sec-2-1">
        <title>The architecture of the Qristal system is described on figure 1 :</title>
        <p>
          Our company is responsible for the indexing process of Qristal. Moreover, it ensures the integration and
interoperability between all linguistic modules. Both English and Italian modules were developed by Expert
System Company. The Portuguese module was developed by the Priberam Company which also takes part in
CLEF 2005 for Portuguese monolingual. The Polish module was developed by the TiP Company. These modules
were developed within the European project TRUST [
          <xref ref-type="bibr" rid="ref3">9</xref>
          ] (Text Retrieval Using Semantic Technologies). Note
that currently, for another European project (M-CAST, Multilingual Content Aggregation System based on Trust
Search Engine), the same partners develop a client-server version of this system in order to exploit digital
resources of libraries.
2.1
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Multicriteria indexing</title>
      <p>While indexing documents, the technology automatically identifies the document language of and the system
calls the corresponding language module. There are as many indexes as languages identified in the corpus.
Documents are treated per blocks. The size of each block is approximately 1 kilobyte. Block limits are settled on
the end of sentences or paragraphs. This size of block (1 kb) appeared to be optimal during our tests. Some
indexes relate to blocks like fields or taxonomy whereas other relate to words, like idioms or named entities (see
figure 2).</p>
      <p>Each linguistic module processes a syntactic and semantic analysis for each block to be indexed. It fills a
complete structure of data for each sentence. This structure is passed to the general processor that uses it to
increment the various indexes. Figure 2 describes the linguistic processes launched while indexing, question
analyzing and answer extracting. This description is accurate for the French module. Other language modules are
very close to that framework but don't always include all its elements. For example, English and Italian modules
do not include an indexing based on heads of derivation.
Texts are converted into Unicode. Then, they are divided into one kilobyte blocks. This reduces the index size as
only the number of occurrences per block is stored for a given lemma. This number of occurrences is used to
infer the relevance of each block while searching a given lemma in the index. In fact we here use lemmas but the
system stores heads of derivation and not lemmas. For example, symmetric, symmetrical, asymmetry,
dissymmetrical or symmetrize will be indexed in the same entry : symmetry.</p>
      <p>Each text block is analyzed syntactically and semantically. Considering results of this analysis, 8 different
indexes are built for:
• heads of derivation. A head of derivation can be a sense for a word. In French, the verb voler has 2 different
meanings (to steal or to fly). The meaning "dérober" (to steal) will lead to vol (robbery), voleur (thief)
or voleuse (female thief). The second meaning, "se mouvoir dans l'air" (to fly), will lead to vol (flight),
volant (flying as an adjective), voleter ( to flutter) or envol (taking flight) and all its forms.
• proper names. If they appear in our dictionaries.
• idioms. Those idioms are listed in our idioms dictionaries. They encompass approximately 50 000 entries,
like word processing, fly blind or as good as your word.
• named entities. Named entities are extracted from texts. George W. Bush or Defense Advanced Research</p>
      <p>Project Agency are named entities.
• concepts. Concepts are nodes of our general taxonomy. 2 levels of concepts are indexed. The first level lists
256 categories, like "visibility". The second level, actually the leaves of our taxonomy, lists 3387
subcategories, like "lighting" or "transparency",
• fields. 186 fields, like "aeronautics", "agriculture", etc.,
• question and answer types for categories like "distance", "speed", "definition", "causality", etc.,
• keywords of the text.</p>
      <p>For each language, the indexing process is similar. Extracted data are the same. Thus, the handling of those data
is independent of their original language. This is particularly important for cross language question answering.
For the French language, the rate of correct grammatical disambiguation (distinction between
name-verbadjective-adverb) is higher than 99%. The rate of semantic disambiguation is approximately 90% for 9 000
polysemous words and approximately 30 000 senses for these words. Note that this number of senses is markedly
inferior to the Larousse one (Larousse is one of the most famous French dictionaries). Note however that our
idioms dictionary covers a large number of the senses mentioned in this kind of dictionaries. The indexing speed
varies between 200 and 400 Mo per hour with a Pentium 3 GHz, according to the size and number of indexed
files.</p>
      <p>Indexing question types is undoubtedly one of the most original aspects of our system. While the analysis of the
blocks is being made, possible answers are located. For example, a name of function for a person (like baker,
minister, director of public prosecutions), a date of birth (like born on April 28, 1958), a causality (like due to
snow drift or because of freezing), a consequence (like leading to serious disruption or facilitating the
management of the traffic). This caused the block to be indexed like being able to provide an answer for a given
question type.</p>
      <p>
        Presently, our question typology includes 86 types of questions. Those types are divided into two subcategories:
factual types and non factual types. Factual types are dimension, surface, weight, speed, percentage, temperature,
price, number of inhabitants or work of art. Nonfactual types are form, possession, judgement, goal, causality,
opinion, comparison or classification. For the EQueR evaluation [3] [
        <xref ref-type="bibr" rid="ref2">8</xref>
        ], 492 questions out of 500 were classified
according to this typology with only 6 errors. For CLEF 2005, results were as follows:
      </p>
      <sec id="sec-3-1">
        <title>Good choice</title>
      </sec>
      <sec id="sec-3-2">
        <title>French</title>
        <p>95.5 %</p>
      </sec>
      <sec id="sec-3-3">
        <title>English</title>
        <p>87.0 %</p>
      </sec>
      <sec id="sec-3-4">
        <title>Italian</title>
        <p>74.5 %</p>
      </sec>
      <sec id="sec-3-5">
        <title>Portuguese</title>
        <p>91.5 %
Building a keyword index for each text is also peculiar to our system. Dividing text into blocks made it
compulsory. Isolated blocks cannot explicitly mention main subjects of the original text although sentences of
these blocks relate to these subjects. The keyword index makes it possible to add contextual information about
the main subjects of the text for blocks. Keywords can be a concept, a person, an event, etc.
1.2</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Answer extraction</title>
      <p>After the user typed its question, it is syntactically and semantically analyzed by the system. Question type is
inferred. We would like here to draw the attention to the fact that questions are shorter than texts. This lack of
context makes the semantic analysis of the question more dubious. That's why the semantic analysis processed on
the question is more comprehensive than the analysis processed on texts. Moreover, users have the possibility to
interactively force a sense. This possibility, however, was not used for CLEF as the entire process was automatic.
The result of the semantic analysis of the question is a weight for each sense of each word recognized as a pivot.
For example, sense 1 is recognized with 20%, sense 2 with 65% and sense 3 with 15%. This weight, together
with synonyms, question and answer types or concepts, is considered while searching the index. Thus all senses
of a word are taken into account during the index search. This prevents from dramatic consequences due to errors
in the semantic disambiguation while making the most of good analysis.</p>
      <p>After question analysis, all indexes are searched and the best ranked blocks are analyzed again. As one can notice
on figure 2, the analysis of the selected blocks is close to the analysis processed while indexing or question
analyzing. On top of this "classic" analysis, a weight for each sentence is inferred. This weight is based on the
number of words, synonyms and named entities found in this sentence, the presence of an answer corresponding
to the question type and a correspondence between the fields and domain.</p>
      <p>
        After this analysis, sentences are ranked. Then, an additional analysis is processed to extract named entities,
idioms or lists that match the answer. This extraction relies on the syntactic characteristics of those groups.
For a question on a corpus located on a hard disk, the response time is approximately 3 seconds with a Pentium 3
GHz. On the Web, first answers are provided after 2 seconds. Then the system computes a progressive refining
during ten seconds, according to user's parameters like the number of words, the number of analyzed pages, etc.
We tested many answer justification modules, mostly implemented from Web [4], [
        <xref ref-type="bibr" rid="ref1">7</xref>
        ] or [
        <xref ref-type="bibr" rid="ref7">13</xref>
        ]. Our technology
enables, as an option, to use such a module of justification. It consists in searching the web with the words of the
question looking for potential answers the system inferred. However this process is seldom selected by users as it
increases the response time of a few seconds. It was not used in CLEF 2005 either. The only justification module
we used was an internal module which makes the most of the semantic information for proper names enclosed in
our dictionaries. For more than 40 000 proper names, we possess information about the country of origin, the
year of birth and death, the function for people, country, the area and population for a city, etc. We think this
justification module is at the origin of some "unjustified" answers. As a matter of fact, it caused the system to
rank first a text including the answer even if the system did not find any clear justification of that answer in the
text.
      </p>
      <p>For cross language question answering, English is used as pivot language. The fact that most users are only
interested in documents in their own language and English motivated that choice. Thus, for cross language
answering, the system processes generally only one translation. For this evaluation, both Portuguese to French
and Italian to French runs required two translations: from source language to English and then from English to
French. QRISTAL does not use any Web Services for translation because of response time. Only words or
idioms recognized as pivots are translated.
3</p>
    </sec>
    <sec id="sec-5">
      <title>Results for CLEF 2005</title>
      <p>QRISTAL was evaluated for CLEF 2005 for French to French, English to French, Portuguese to French and
Italian to French. That is 1 monolingual and 3 multilingual campaigns. For each one of these tasks, we processed
only one run. Note that results obtained in CLEF 2005 could have been obtained with the commercial version of
our Qristal software, in the version of May 2005.</p>
      <sec id="sec-5-1">
        <title>French-French</title>
      </sec>
      <sec id="sec-5-2">
        <title>English</title>
      </sec>
      <sec id="sec-5-3">
        <title>French</title>
      </sec>
      <sec id="sec-5-4">
        <title>Italian-French</title>
      </sec>
      <sec id="sec-5-5">
        <title>Portuguese</title>
      </sec>
      <sec id="sec-5-6">
        <title>French</title>
        <p>For French to French, these results are better than those we obtained for the EQueR campaign. That is 64% for
CLEF 2005 and 52% for EQueR 2004. Compared to EQueR, CLEF proposed additional difficulties as an exact
answer is required. Only a passage of 50 maximum characters was asked for EQueR. On the contrary it seems the
level of difficulty of the questions of CLEF is lower than those of EQueR which included for example research of
lists as answers. This overall improvement of our performances validates the developments we did last year and
particularly for the extraction of definitions.</p>
      </sec>
      <sec id="sec-5-7">
        <title>Right</title>
        <p>Results per category are as follows:
100,0%
0,14 7 ,031
0
,
0
Temporally
restricted
factoid
questions
0
3
,
25 0
,
0
5
1
,
0
5
4
,
0</p>
        <p>French-French
One can notice the quality of answers is lower for cross lingual answering. In fact, the English to French run finds
approximately 60% of the answers found in the French to French run. The Portuguese to French run finds 57% of
the French to French run. Because of a bug we didn't manage to solve during the CLEF campaign, the Italian
module did not translate pivot words to English. Thus, for the Italian to French run, results were computed only
using words common in both languages. Fortunately, most proper names are identical between French and
Italian. Anyway, taxonomy, question types and fields were used for this Italian to French run.
Precision and recall for NIL questions are quite poor. Nil questions are questions without any existing answer in
the corpus. Our search engine was designed to find answers (!) and strategies dedicated to the detection of
questions without any answer are quite unsatisfactory. Actually, the main routine in this process compares the
possible date of the question and the date of text to remove texts anterior to the date of the question.
The difference between Italian and both English and Portuguese was explained before. It is due to the fact that no
translation is processed from Italian to English. For the other language pairs, we tried to determine the reasons of
that gap. Thus, we scanned all translations and list words that had inadequate or inexistent translations. Results of
this work are presented in the following table.</p>
        <sec id="sec-5-7-1">
          <title>Total of pivot words</title>
          <p>Not translated from source language to English
Not translated from English to French
Badly translated from English to French
Total for translation mistakes</p>
        </sec>
        <sec id="sec-5-7-2">
          <title>English-French Portuguese-French Italian-French 623</title>
          <p>This table underlines the relation between errors in translation and the performance of the multilingual system.
Portuguese module is rather more precise than the English module but it is penalized by the double translation,
from Portuguese to English and then from English to French. For example, for question 11 (Which French Prime
Minister committed suicide?) Prime and minister are translated into French as prime and ministre quite far from
the correct translation that is premier ministre !
Then we had a closer look to questions where the monolingual process finds the answer but the cross language
does not. This leads us to the following remark. Questions are defined by reading the corpus and, deliberately or
not, people formulating questions tend to reuse words or expressions mentioned in the text of the identified
answer. On one hand, this influences the capacity of the system and the importance of each module in the overall
process. For example, the use of synonyms is not that important for CLEF as it normally is. On the other hand,
for cross language question answering, translations can be fuzzy and potentially quite far from the targeted word
or expression especially when one uses English as an intermediate language. This way, translated words are quite
often different from the terms mentioned both the question and the answer.</p>
          <p>For question 10 Quel professeur de Bonn a reçu le prix Nobel d'économie ? (Which professor from Bonn
received the Nobel Prize for Economics?), the French module extracts the noun phrase prix Nobel d'économie
(Nobel Prize in economy). In English, translation provides the words professeur, Bonn, recevoir, Nobel, Prix and
économie but neither prix Nobel nor prix Nobel d'économie.</p>
          <p>Consider question 55 Quel poste tenait Silvio Berlusconi avant qu'il ne démissionne? for French, What minister
was Silvio Berlusconi prior to his resignation for English and Que ministério ocupava Silvio Berlusconi antes da
sua demissão? for Portuguese. The word minister in English and ministério translated into minister by the
Portuguese module are translated into French as ministère (ministry). But the answer provided by the French
module is président du Conseil italien extracted from "Décidant finalement de renoncer à demander un vote de
confiance au Parlement, le président du conseil italien, Silvio Berlusconi, a remis, jeudi 22 décembre dans
l'après-midi, sa démission au président de la République, Oscar Luigi Scalfaro." One can notice that the answer
has nothing to do with a ministry. Moreover, the English word resignation correctly translated into French as
resignation is quite far from the word démission (abdication).</p>
          <p>To determine the various roles of every part of our system, we disconnected some modules and measured the
overall performance. With the 200 questions of CLEF, the most important module was the question and answer
type extractor. Disconnecting it causes an 11.5% drop for the monolingual campaign. This module is used to
index, to search the index, and to extract exact answers from blocks. Other modules have secondary roles. We
noted a drop of 2% by disconnecting synonyms dictionaries and a 3% drop by giving the same weight to all
pivots. Note however that main components such as the part of speech tagger are almost impossible to test
separately as all the system relies on it.</p>
          <p>
            Priberam, the company responsible for the Portuguese module in our engine, participated in CLEF 2005 in the
Portuguese to Portuguese evaluation track. It is interesting to note that they obtained results very similar to our
results for the monolingual run [1] [2]. This seems to objectively validate our common choices and our resulting
technology that is very close to the best systems available for English which have participated for many years
now in this type of evaluation via the TREC evaluation campaigns [6] [
            <xref ref-type="bibr" rid="ref8">14</xref>
            ].
4
          </p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>Outlines</title>
      <p>For 4 years now we sell out our question answering system on the French market. According to user's reactions
and remarks we established a list of compulsory elements for such a system not to be directly rejected by users:
• Response time must not exceed 3 seconds, and preferably 1 or 2 seconds. By any means, a first answer
must be displayed within this period.
• Success rate must approach 100%. A system providing only one answer out of 3 or less is acceptable only
by a reduced number of users.
• Questions like those used for TREC or CLEF represent only a part of user's questions. Users often types
"why" or "how" questions. Such a system has to handle it correctly.</p>
      <p>
        An 80% of correct answers for monolingual search and 60% for multilingual is a minimum to convince a large
audience of the interest of question answering systems. To reach such a level of performance, while reducing
response time, very few approaches are available. Unfortunately, it is not possible to use strategies based on the
Web redundancy [
        <xref ref-type="bibr" rid="ref4">10</xref>
        ] [
        <xref ref-type="bibr" rid="ref6">12</xref>
        ]. Actually, user's search often relates to specific corpus not redundant on the Web.
Moreover, parallel research strategies or parallel justification using the Web take too long and are therefore
inadequate.
      </p>
      <p>However, we identified the following approaches to improve our technology:
• A general improvement of our resources. Particularly the semantic disambiguation process and the
translation dictionaries.
• A refinement of the typology of questions and a precise definition of named entities expected in the answer
for various question types would be of higher interest.
• An improvement of the answer delimitation process would reduce the number of "inaccurate" answers.
• Handling the presentation of documents. Documents are considered as rough text, without taking into
account possible tags, titles, paragraphs, bolded parts, etc.
• The use of databases for question answering. The best translation systems use translation memory.</p>
      <p>Question answering systems could use memory as well. This process would imply the construction of a
database storing factual predicates. This construction could be based on an automatic analysis of the
Web. We could imagine storing questions and related answers users ask the system as well. A major
interest of such databases is that accessing them is very quick. Thus, by using them, the system can
process an answer instantly and then search for justification - or invalidation - in documents of the
corpus.
• A specific handling for questions that cannot have an answer on the Web or in the corpus. Questions like
What is the weather forecast for tomorrow? cannot be addressed by question answering systems based
on corpus analysis. For those questions, you would rather send a well formatted request to weather
forecast dedicated web sites than to general search engines. Same remarks concerning questions about
itineraries or prices for which specialized sites are more likely to generate an appropriate answer, if
there is at least one answer to the question, of course !.</p>
      <p>As treating non factual question is of higher interest we encourage evaluation campaigns such as CLEF to take
them into account [5]. Note that the evaluation of those questions and answer pairs is more difficult.
Analyzing the questions and user's reactions in front of provided answers underlines the gap between the words
used in the question and those mentioned in the expected answer. This especially occurs for questions like what
do clients think about the Large hotel in Berlin? or which guarantees offer my blue card? Lexical (synonyms,
analogies) or thematic assistances could help the user to better find expected answers.
More technically, the M-CAST European project (http://www.m-cast.infovide.pl) in which our company as well
as our Italian, Portuguese and Polish partners take part will enable us to test our system in a professional
environment.
5</p>
    </sec>
    <sec id="sec-7">
      <title>Conclusion</title>
      <p>QRISTAL is the first question answering system marketed for general public and professionals. Results obtained
for the EQUER evaluation, largely confirmed by those we obtained during CLEF evaluation, show that the
intensive use of NLP technologies for analyzing the question, indexing texts and extracting answers leads to a
good outcome. The fact that Priberam, which uses the same framework, obtained very close results for
Portuguese encourages this assertion.</p>
      <p>Our results, to be compared to the best international prototypes, can however be regarded as insufficient,
particularly when it comes to Web searching. As we use a meta-search engine, that is an engine using the results
of other search engines of the Web, we have no control over the indexation process. Moreover, downloading
pages provided by Web search engines is time consuming and therefore limited. Thus, Web searching with our
present technology is not as accurate as corpus searching.</p>
      <p>One can assume that present boolean search engines will be replaced by NLP systems in several years.
Nevertheless, demonstrating the advantages of such systems and revealing present weaknesses of boolean search
engines will take quite a long time, partly because experts in this domain often are Boolean search experts!</p>
    </sec>
    <sec id="sec-8">
      <title>Acknowledgments</title>
      <p>The authors thank Bruno Wieckowski and all engineers and linguists that took part in the development of
QRISTAL. They also thank the Italian company Expert System and the Portuguese company Priberam for
allowing them to use their modules for question analysis in English, Italian and Portuguese. They finally thank
the European Commission which supported and still supports our development efforts through TRUST and
MCAST projects.</p>
      <p>Last but not least, authors thank Carol Peters, Alessandro Vallin, Danilo Giampiccolo and Christelle Ayache for
the remarkable organization of CLEF.
[1] AMARAL C., LAURENT D., MARTINS A., MENDES A., PINTO C. (2004), Design &amp; Implementation of a
Semantic Search Engine for Portuguese, Proceedings of the Fourth Conference on Language Resources and
Evaluation.
[2] AMARAL C., FIGUEIRA H., MARTINS A., MENDES A., MENDES P., PINTO C. (2005), Priberam's question
answering system for Portuguese, Working Notes for the CLEF 2005 Workshop, 21-23 September, Wien,
Austria.
[3] AYACHE C., GRAU B., VILNAT A. (2005), Campagne d'évaluation EQueR-EVALDA : Évaluation en
question-réponse, TALN 2005, 6-10 juin 2005, Dourdan, France, tome 2. – Ateliers &amp; Tutoriels, p. 63-72.
[4] CLARKE C. L. A., CORMACK G. V., LYNAM T. R. (2001), Exploiting Redundancy in Question Answering,
Proceedings of 24th Annual International ACM SIGIR Conference (SIGIR 2001), p. 358-365.
[5] GRAU B.. (2004), L'évaluation des systèmes de question-réponse, Évaluation des systèmes de traitement de
l'information, TSTI, p. 77-98, éd. Lavoisier.
[6] HARABAGIU S., MOLDOVAN D., CLARK C., BOWDEN M., WILLIAMS J., BENSLEY J. (2002), Answer Mining
by Combining Extraction Techniques with Abductive Reasoning, Proceedings of The Twelfth Text Retrieval
Conference (TREC 2003).</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>JIJKUN V.</given-names>
            , MISHNE G.,
            <surname>DE RIJKE M.</surname>
          </string-name>
          ,
          <string-name>
            <surname>SCHLOBACH S.</surname>
          </string-name>
          ,
          <string-name>
            <surname>AHN D.</surname>
          </string-name>
          ,
          <string-name>
            <surname>MÜLLER K.</surname>
          </string-name>
          (
          <year>2004</year>
          ), The University of Amsterdam at QALEF 2004, Working Notes of the Workshop of CLEF 2004, Bath,
          <fpage>15</fpage>
          -
          <lpage>17</lpage>
          september
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [8]
          <string-name>
            <surname>LAURENT D.</surname>
          </string-name>
          ,
          <string-name>
            <surname>SEGUELA P.</surname>
          </string-name>
          (
          <year>2005</year>
          ), QRISTAL, système de Questions-Réponses,
          <string-name>
            <surname>TALN</surname>
          </string-name>
          <year>2005</year>
          ,
          <volume>6</volume>
          -
          <fpage>10</fpage>
          juin
          <year>2005</year>
          , Dourdan, France, tome
          <volume>1</volume>
          . -Conférences principales, p.
          <fpage>53</fpage>
          -
          <lpage>62</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [9]
          <string-name>
            <surname>LAURENT D.</surname>
          </string-name>
          ,
          <string-name>
            <surname>VARONE M.</surname>
          </string-name>
          ,
          <string-name>
            <surname>AMARAL C.</surname>
          </string-name>
          ,
          <string-name>
            <surname>FUGLEWICZ P.</surname>
          </string-name>
          (
          <year>2004</year>
          ),
          <article-title>Multilingual Semantic and Cognitive Search Engine for Text Retrieval Using Semantic Technologies</article-title>
          ,
          <source>First International Workshop on Proofing Tools and Language Technologies</source>
          , Patras, Grèce.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [10]
          <string-name>
            <surname>MAGNINI</surname>
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>NEGRI</surname>
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>PREVETE R.</surname>
          </string-name>
          , TANEV H. (
          <year>2002</year>
          ),
          <article-title>Is It the Right Answer? Exploiting Web Redundancy for Answer Validation</article-title>
          ,
          <source>Proceedings of the 40th Annual Meeting of the ACL</source>
          , p.
          <fpage>425</fpage>
          -
          <lpage>432</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [11]
          <string-name>
            <surname>MAGNINI</surname>
            <given-names>B.</given-names>
          </string-name>
          , VALLIN A.,
          <string-name>
            <surname>AYACHE C.</surname>
          </string-name>
          , ERBACH G.,
          <article-title>PEÑAS A</article-title>
          .,
          <string-name>
            <surname>DE RIJKE M.</surname>
            ,
            <given-names>ROCHA P.</given-names>
          </string-name>
          , SIMOV K., SUTCLIFFE R.
          <article-title>(2004), Overview of the CLEF 2004 Multilingual Question Answering Track</article-title>
          ,
          <source>Working Notes of the Workshop of CLEF</source>
          <year>2004</year>
          , Bath,
          <fpage>15</fpage>
          -
          <lpage>17</lpage>
          september
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [12]
          <string-name>
            <surname>MONZ</surname>
            <given-names>C.</given-names>
          </string-name>
          (
          <year>2003</year>
          ), From Document Retrieval to Question Answering,
          <source>ILLC Dissertation Series 2003-4</source>
          , ILLC, Amsterdam.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [13]
          <string-name>
            <surname>NEUMANN G.</surname>
          </string-name>
          ,
          <string-name>
            <surname>SACALEANU B.</surname>
          </string-name>
          (
          <year>2004</year>
          ),
          <article-title>Experiments on Robust NL Question Interpretation and Multilayered Document Annotation for a Cross-Language Question/Answeringg System</article-title>
          ,
          <source>Working Notes of the Workshop of CLEF</source>
          <year>2004</year>
          , Bath,
          <fpage>15</fpage>
          -
          <lpage>17</lpage>
          september
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [14]
          <string-name>
            <surname>VOORHEES E. M..</surname>
          </string-name>
          <article-title>(2003), Overview of the TREC 2003 Question Answering Track</article-title>
          , NIST,
          <fpage>54</fpage>
          -
          <lpage>68</lpage>
          (http://trec.nist.gov/pubs/trec12/t12_proceedings.html).
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>