<!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>Contextual Approach for Paragraph Selection in Question Answering Task</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Hapnes Toba</string-name>
          <email>hapnes.toba@ui.ac.id</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Syandra Sari</string-name>
          <email>syandra.sari@ui.ac.id</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Mirna Adriani</string-name>
          <email>mirna@cs.ui.ac.id</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ruli Manurung</string-name>
          <email>maruli@cs.ui.ac.id</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Information Retrieval Laboratory, Faculty of Computer Science, University of Indonesia Depok Campus</institution>
          ,
          <country country="ID">Indonesia</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>This year we participated in the English monolingual paragraph selection task at ResPubliQA 2010. Our general strategy is to find the supporting word context from query and candidate passages during the paragraph selection. We use the techniques of state-of-the art publicly available question answering systems, i.e. Open Ephyra and JIRS, and the random projection implementation in the Semantic Vectors package to evaluate the word context. To strengthen the paragraph selection, besides the context evaluation, we also use n-gram overlapping and textual containment. Our approach has a c@1 measure of 0.73 for our pattern-based context configuration and 0.64 for our n-gram-based context configuration.</p>
      </abstract>
      <kwd-group>
        <kwd>context supporting</kwd>
        <kwd>passage retrieval</kwd>
        <kwd>random projection</kwd>
        <kwd>n-gram overlapping</kwd>
        <kwd>textual containment</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1 Introduction</title>
      <p>
        Question Answering (QA) is a specific form of information retrieval (IR) that
seeks to produce an exact answer given a natural language question. An automated
QA system tries to retrieve explicit answers in the form of a single answer or snippets
of text rather than a whole document or set of documents. The main techniques that
mostly have been used in current QA research are semantic analysis using semantic
role labeling [
        <xref ref-type="bibr" rid="ref21">20</xref>
        ], named entity recognition [
        <xref ref-type="bibr" rid="ref6">5</xref>
        ], path dependency [
        <xref ref-type="bibr" rid="ref6">5</xref>
        ], semantic
markup [
        <xref ref-type="bibr" rid="ref13">12</xref>
        ], n-gram passages [
        <xref ref-type="bibr" rid="ref12 ref8">2, 7, 11</xref>
        ], statistical methods [
        <xref ref-type="bibr" rid="ref14 ref15">13, 14</xref>
        ], combinations of
semantic structures and probabilistic approaches [
        <xref ref-type="bibr" rid="ref16">15</xref>
        ], and combinations of semantic
structures and automated reasoning [
        <xref ref-type="bibr" rid="ref17 ref18 ref19">16, 17, 18</xref>
        ]. There is no ultimate technique, each
approach has its own role, application domain, and tasks [
        <xref ref-type="bibr" rid="ref20">19</xref>
        ].
      </p>
      <p>
        This year’s ResPubliQA1 evaluation campaign is a continuation from last year
which tries to evaluate QA performance in a specific context, i.e. the legal domain
[
        <xref ref-type="bibr" rid="ref22">21</xref>
        ]. Since this year is our first participation, we decided to compete in the English
monolingual paragraph selection task. We experiment with various QA strategies that
are supported by the notion of word context, which return passages that contain
candidate answers. For this purpose, we develop a context supporting paragraph
      </p>
      <sec id="sec-1-1">
        <title>1 http://celct.isti.cnr.it/ResPubliQA/</title>
        <p>
          selection strategy which validates the passage retrieval mechanisms from two
stateof-the-art publicly available QA systems, Open Ephyra [1] and JIRS [
          <xref ref-type="bibr" rid="ref8">2, 7</xref>
          ].
        </p>
        <p>Our general hypothesis in this experiment is that, in a specific domain, the context
of a question is near to the context of candidate paragraphs that are suggested during
the passage retrieval. This hypothesis is a generalization of the distributional
hypothesis from the word space methodology, which says that words with similar
meaning tend to occur in similar contexts [3]. We took the publicly available random
projection implementation in Semantic Vectors [4] as the context supporting system
of our approach. Our observation during this experiment will be: how to employ word
context to support passage retrieval performed by language model and n‐gram
approaches. To answer this research question, our approach tries to boost the
influence of word context during paragraph selection.</p>
        <p>In this paper we describe the approach of our context supporting strategy and the
results obtained in the monolingual English paragraph selection task. The rest of the
paper is structured as follows: in section 2 we describe in general the related systems
whose techniques were used in our approach, namely Open Ephyra, JIRS and
Semantic Vectors. The details of our approach will be covered in section 3. Section 4
will show some results and analysis in the paragraph selection task of this year’s
ResPubliQA. Finally, some conclusions and suggestions for future work will be given
in section 5.
2</p>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>QA Pipeline and Word Space Methodology</title>
      <p>Open Ephyra2 and JIRS3 are two QA systems which offer comprehensive pipelines.
They base their passage retrieval strategies on, respectively, language models and
ngram structures of the passages. Both strategies rely on the probability and sequences
of adjacent words from query-passage pairs, but do not really observe the word in
context. Alternatively, Semantic Vectors4 offers the possibility to observe the word
context in a domain by implementing the word space methodology.</p>
      <sec id="sec-2-1">
        <title>2.1 Pattern-based Question Answering</title>
        <p>
          Open Ephyra (OE) uses a pattern learning approach to categorize questions [
          <xref ref-type="bibr" rid="ref6">1, 5</xref>
          ]. OE
can learn question-answer pairs and uses standard IR systems, such as Indri, to fetch
text snippets that are suitable for pattern extraction. It consists of four main modules:
a question analyzer, query generator, search engine, and answer extractor. Each
module can be used independently and is thus suitable for experimenting with
multiple approaches to question-answering as one pipeline system.
        </p>
        <p>There are two main steps for the pattern-learning approach in OE:
1. The first is to learn the question patterns from question templates according to
each question type. The aim of this step is to interpret the questions and
2 http://www.ephyra.info
3 http://sourceforge.net/projects/jirs/
4 http://semanticvectors.googlecode.com/
transform them into queries. The question templates need to be manually
developed according to various interrogative sentences that are independent for
each natural language.
2. The second step is to learn the answer patterns from question-answer pairs. The
aim of this second step is to extract answer candidates from relevant document
snippets and to rank them.</p>
        <p>In our experiment, we only used the first step to develop an appropriate set of
question patterns for each question type according to the training data from last year’s
ResPubliQA. A recognized question pattern for a given question is essential in order
to extract important keywords (i.e. target, context and property) for querying
purposes. The retrieval phase in OE is done within the Indri search engine that
searches for passages in documents - based on the recognized query keywords - which
could contain the answer candidates.</p>
      </sec>
      <sec id="sec-2-2">
        <title>2.2 n-Gram-based Question Answering</title>
        <p>
          The question answering module in JIRS is an extension of the JIRS passage retrieval
system as described in [
          <xref ref-type="bibr" rid="ref8">7</xref>
          ]. The general architecture of JIRS is comparable to OE as
described in the previous sub-section. A given question will be classified to an
appropriate class that will be further used by the passage retrieval algorithm. JIRS’s
retrieval algorithm is based on the ordering of n- neighboring words extracted from a
passage, which is called as Clustered Keyword Positional Distance (CKPD).
        </p>
        <p>
          JIRS is based on the idea that in a large document collection, an n-gram related
with a question will be found in the collection at least once [
          <xref ref-type="bibr" rid="ref12">11</xref>
          ]. Only passages with
n-grams that contain question terms are returned. The weight of each passage is
calculated according to the similarity between the question and the passage n-grams.
The similarity of a passage with the question is greater if the passage shares longer
structures with the question [2]. A brief introduction of JIRS can found in [
          <xref ref-type="bibr" rid="ref12">11</xref>
          ], while
the complete CKPD algorithm can be found in [2].
        </p>
      </sec>
      <sec id="sec-2-3">
        <title>2.3 Semantic Vectors</title>
        <p>Semantic Vectors is an open source package that can be used to build context vectors
of word concepts in a specific domain. It implements word space methodology [3] by
applying random projections of words in the document collection. Words in Semantic
Vectors are represented as vectors in a high dimensional space, where words or
documents that have related meanings are in close proximity. By applying random
projection, the computational resources that are usually required for computing
semantic similarity, as for instance in Latent Semantic Analysis (LSA), can be
minimized.</p>
        <p>
          The random projection strategy can be summarized in two main steps [
          <xref ref-type="bibr" rid="ref9">3, 4, 8</xref>
          ]:
1. Step 1: Build the term vectors.
        </p>
        <p>For each document, make an N-dimensional ternary index vector by placing a
small number, k, of -1’s and +1’s (e.g., ten of each; k = 10) at random among the
N-dimensional index vector, the rest will be 0’s.
2. Step 2: Build the document vectors</p>
        <p>Scan through the documents. Every time the word appears, add the index vector
to row w of matrix G, where G is a (M x N) matrix, M is the number of words in
the collection and N is the number of reduced columns.</p>
        <p>The Semantic Vectors package uses the Apache Lucene API5 to create a word
space model from a term document matrix, using random projection to perform
dimensionality reduction.</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3 Experiments</title>
      <p>3.1</p>
      <sec id="sec-3-1">
        <title>Data Preparation</title>
        <p>For the data preparation, from the JRC-ACQUIS6 and EUROPARL7 corpus we have
created a passage index based on the paragraph segmentations. In total we have
around 1.5 million passages. We created separate indexes for each information
retrieval system that we used in our approach, namely Indri, JIRS and Lucene.</p>
        <p>
          Indri is a search engine that is specially designed for passage retrieval [2] such as
JIRS. The difference between them lies in the retrieval model. Indri’s retrieval model
is based on a combination of language modeling and inference network retrieval
frameworks [
          <xref ref-type="bibr" rid="ref7">6</xref>
          ], while JIRS based its retrieval model on the CKPD algorithm [2].
        </p>
        <p>The Lucene index will be used by the Semantic Vectors package to form the terms
and document vectors [4]. In our approach we choose the value of 2000 for the
number of dimensions. This value is the reduced columns for documents projection
that is considered as the word space.
3.2</p>
      </sec>
      <sec id="sec-3-2">
        <title>System Architecture</title>
        <p>The high level architecture of our approach can be seen in Fig. 1. This architecture is
based on the general framework of question answering systems. The first component
is the question analysis, which normalizes the question (i.e. removes the question
word, stop-words, and performs word stemming), and determines the question type.
We used manually developed question patterns to determine the question types.</p>
        <p>
          After the question analysis step, the system delivers the normalized question to a
query generator based on the techniques that were used in OE [
          <xref ref-type="bibr" rid="ref6">1, 5</xref>
          ], JIRS [2] and
Semantic Vectors [4]. The next step is the information retrieval phase. In our
approach, it is done by the Indri, JIRS or Lucene search engine, which corresponds to
the generated queries. The retrieval results from each search engine are collected in
separated files that will be evaluated by the paragraph selection component.
        </p>
        <p>The main idea during paragraph selection is to evaluate whether supporting word
context can be found among the candidate passages. It checks first the word context</p>
        <sec id="sec-3-2-1">
          <title>5 http://lucene.apache.org/</title>
          <p>
            6 http://wt.jrc.it/lt/Acquis/
7 http://www.europarl.europa.eu/
that is present at the top-1 retrieval of the candidate passages. This is done by
comparing candidate passages from Indri or JIRS with the one retrieved by Semantic
Vectors. If the two systems that were compared returned the same document at the
top-1 retrieval, then we believe that supporting word(s) context was found in the
passages that were compared, or in other words the documents “shared” the same
context. Otherwise, the paragraph selection will be determined by applying n-gram
overlapping, textual containment [
            <xref ref-type="bibr" rid="ref10 ref11">9, 10</xref>
            ], and answer type validation from the
namedentity of the expected answer type.
The above explained architecture was tested using the data from ResPubliQA 2009
for all 500 questions, the results of which can be seen in Table 1.
          </p>
          <p>From this initial experiment, we can see that our proposed approach, as described
in previous sub-section, outperformed the baseline accuracy of Indri and JIRS by
6.8% and 6.2% respectively. The graphical interpretation from the above
experimental result is presented in Fig. 2.</p>
        </sec>
      </sec>
      <sec id="sec-3-3">
        <title>3.4 Pattern Based – Context Support</title>
        <p>
          For our first submitted run, we combined the technique of pattern-based question
answering, as proposed in [
          <xref ref-type="bibr" rid="ref6">1, 5</xref>
          ] with the results from Semantic Vectors. There are
five question patterns manually developed for each question type: factoid, definition,
reason-purpose, procedure, and opinion. Each question pattern will be responsible for
the expected answer type analysis during the paragraph selection phase. An example
of the developed patterns is shown in Listing 1, for the opinion question type.
QUESTION_TEMPLATE: What is the &lt;CO&gt; opinion of &lt;TO&gt;
        </p>
        <p>ANSWER_TEMPLATE: Opinion: &lt;PO&gt;
what (a|the)? &lt;CO&gt; (position|opinion|feelings|ideas) (with respect
to) &lt;TO&gt;</p>
      </sec>
      <sec id="sec-3-4">
        <title>Listing 1 Example of Question Pattern (Opinion)</title>
        <p>The detailed strategy of the paragraph selection phase can be seen in Listing 2. In
this scenario, the supporting context (the first step in listing 2), is used to select
passages that we believed ‘share’ the same context, and hence they can be used
confidently as the final answer. If the result of Indri and Semantic Vectors did not
return the same passage, we evaluate the top-5 of Indri results by applying n-gram
overlapping (step 2.a) If n-gram overlapping is unsuccessful, i.e. all passages have the
same amount of n-gram overlapping, we use a textual containment strategy to
calculate the best proportion of query terms that can be found in the passages (step
2.b), and at the same time try to find a named-entity that is expected to be present in
the passages (step 2.c). ‘No answer’ will be returned if there is no passage that meets
the conditions in the strategy (step 3). Note that by using containment, passages
whose text is too long will be discarded. This step is used essentially to anticipate the
definition question type, which usually only has one or two terms from the query that
can be found back in the candidate passages.
1. Compare the retrieved passages by Indri and Semantic Vectors. If the
top-1 returned document is the same, then return the passage offered
by Indri as final answer.
2. Otherwise:
a. Get top-5 retrieved passages from Indri retrieval, count the
query-passage n-gram overlapping (unigram, bigram and trigram)
from each passage, return passage with the biggest total n-gram
overlapping as final answer.
b. If the total count of n-gram overlapping of top-5 passages is
all the same, then compare the query supporting text in each
Indri retrieved passages (textual containment). Sort the
passages by the best containment as candidate answers.
c. If the expected answer type is about facts (time, place, number,
organization), definition (about a term), or opinion (a person
name or organization), check the result from step 2.a. If a
named-entity can be found in the first passage, returns it as
final answer. Otherwise, try to find named-entity in the lower
rankings.
3. If there is no passage found that confirm steps 1, or 2, returns No
Answer (NOA).</p>
        <p>Listing 2 Detail Strategy of Scenario 1 (Pattern-based – Context Support)
0008
0001
0026
0027</p>
        <p>p_id=13
doc_id=EP_CRE20090507-EN_cl.xml</p>
        <p>p_id=45
doc_id=EP_CRE20091008-EN_cl.xml</p>
        <p>p_id=13
doc_id=jrc32002D0268
-en.xml
p_id=164
doc_id=EP_TA20090114-EN_cl.xml</p>
        <p>Top-1 SV
Retrieval
EP_CRE20090507</p>
        <p>EN_cl.xml</p>
        <p>As an example from Table 2, the Quest. # 0008 (Name a purpose of MEDIA
Mundus), Indri and SV have both retrieved the same top-1 document
(EP_CRE20090507-EN_cl.xml). According to our strategy, the system should take step 1 in
Listing 2 as the final decision for the paragraph returned.</p>
        <p>
          In another example from Table 2, the Quest. # 0027 (Define children footwear),
Indri and SV have retrieved different documents. The next step is to determine the
best n-gram overlapping (step 2.a) between the top-5 Indri retrieved passages and the
question terms (children footwear). Since all of the top-5 Indri retrieved passages
have only one term in common with the question (i.e. the term children), the system
should now compute the value of textual containment [
          <xref ref-type="bibr" rid="ref10">9</xref>
          ], to determine how well the
n-gram overlapping is in comparison with the length of the passage (step 2.b). From
last year’s training data, we decided to use a minimum threshold value of 0.02 for
textual containment. In the case of Quest. # 0027, all of the top-5 retrieved passages
have a textual containment value lower than the threshold, hence the system will
return ‘NOA’ as the final answer (step 3).
        </p>
      </sec>
      <sec id="sec-3-5">
        <title>3.5 n-Gram Passage Retrieval – Context Support</title>
        <p>For our second submitted run, we combined the results of JIRS and Semantic Vectors
to retrieve passages which could contain answer candidates. The detailed strategy of
the paragraph selection phase can be seen in Listing 3.
1. Compare the retrieved passages from JIRS and Semantic Vectors. If
the top-1 returned document is the same, then return the passage
offered by JIRS as the final answer.
2. Otherwise:
a. Get the top-5 passages from JIRS retrieval, count the
querypassage n-gram overlapping (unigram, bigram and trigram) from
each passage, return passage with the biggest total n-gram
overlapping as the final answer.</p>
      </sec>
      <sec id="sec-3-6">
        <title>Listing 3 Detail Strategy of Scenario 2 (n-Gram Passage Retrieval – Contexts Support)</title>
        <p>b. If all of the top-5 JIRS passages have the same total count of
n-gram, then count the n-gram overlapping (unigram, bigram and
trigram) of the query in each paragraph of the retrieved top-1
Semantic Vector document, return passage with the biggest n-gram
overlapping as the final answer.
c. If there is more than one paragraph from the SV top-1 document
have the same total count of n-gram then return paragraph with
the best textual containment as the final answer.</p>
      </sec>
      <sec id="sec-3-7">
        <title>Listing 3 (cont’d) Detail Strategy of Scenario 2 (n-Gram Passage Retrieval – Contexts</title>
      </sec>
      <sec id="sec-3-8">
        <title>Support)</title>
        <p>The first paragraph selection strategy is to compare the top-1 retrieved passage
from JIRS and the one retrieved by Semantic Vectors. If both retrieval systems
suggested the same document, then we took the passage returned by JIRS as the final
answer. Otherwise, we followed the same strategy as scenario 1 to select the best
paragraph. But now, we used the top-1 suggested document from Semantic Vectors as
the final paragraph decision. Table 3 gives some examples of the system’s decision
according to this second scenario for the test questions from ResPubliQA 2010. The
explanation for Table 3 is similar to the explanation for Table 2 in the previous
subsection.</p>
        <p>In Scenario 2, there was no strategy developed for the NOA-answer. The reason
for this is considering the final decision rule that selects paragraphs from only one
document, i.e. the Semantic Vectors top-1 retrieved document - with no textual
containment threshold - and thus, there must be one paragraph returned as the final
answer.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4 Results and Analysis</title>
      <p>JIRS-Semantic Vectors (uiir102PSenen). These two configurations differ in the way
passages are refined during the paragraph selection phase (cf. Section 3).</p>
      <p>If we observe the accuracy of each question type in detail (Table 5), the
‘Definition’ question type gives the lowest accuracy in each configuration, i.e. 0.43
(Scenario 1) and 0.37 (Scenario 2). This result indicates that the ‘Definition’ question
type is the most difficult one to be answered, and our strategy is not suitable to answer
this type of question properly. The best accuracy in both scenarios is achieved for the
‘Reason-Purpose’ question type, i.e. 0.87 (Scenario 1) and 0.77 (Scenario 2).</p>
      <p>It is interesting to explore the accuracy of the ‘Procedure’ question type, which
achieved 0.58 accuracy in Scenario 1, and 0.68 in Scenario 2. Most of the question
types have question patterns and question terms that are almost identical from one
question to another; see for example the ‘Opinion’ question pattern in Listing 1. This
is also one of the reasons that Scenario 1 performed better than Scenario 2, except for
the ‘Procedure’ question type that has richer patterns and more answer variations.</p>
      <p>RIGHT ANS. WRONG ANS.</p>
      <p>Sce. 1 Sce. 2 Sce. 1 Sce. 2
13 12 3 3
1 2 6 2
3 4 1 0
3 4 4 2
4 2 0 3
In this paper we have described our context supporting approach in passage retrieval
question answering for the English monolingual task. Our experimental results
showed that in a specific domain, context supporting - as a ‘second-opinion’ decision
system by using random document projection - can improve the performance of the
passage retrieval (paragraph selection) component in a QA system.</p>
      <p>It would be interesting to conduct a further study in how to relate word context in
broader domains, to support open-domain and multilingual question answering. It
would also be interesting to investigate the value of reduced dimensionality from a
document collection that formed the word space during retrieval. In this experiment
we have only used the number of dimensions of 2000, due to technical restrictions.
Perhaps, if the value of the dimension is varied, the context supporting strategy could
perform better.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          <string-name>
            <surname>Schlaefer</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gieselmann</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schaaf</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Waibel</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>A Pattern Learning Approach to Question Answering within the Ephyra Framework</article-title>
          .
          <source>In: LNAI 4188</source>
          , pp.
          <fpage>687</fpage>
          -
          <lpage>694</lpage>
          , Springer-Verlag,
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <string-name>
            <surname>Buscaldi</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rosso</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gómez-Soriano</surname>
            ,
            <given-names>J.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sanchis</surname>
          </string-name>
          , E.:
          <article-title>Answering questions with an n-gram based passage retrieval engine</article-title>
          .
          <source>Journal of Intelligent Information System (82)</source>
          , Springer,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          <string-name>
            <surname>Sahlgren</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>An introduction to random indexing</article-title>
          .
          <source>In: Proceedings of the Methods and Applications of Semantic Indexing Workshop at the 7th International Conference on Terminology and Knowledge Engineering (TKE)</source>
          , Copenhagen, Denmark,
          <year>2005</year>
          . SICS, Swedish Institute of Computer Science.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          <source>Retrieved in March</source>
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          <string-name>
            <surname>Widdows</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ferraro</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Semantic Vectors: A Scalable Open Source Package and Online Technology Management Application</article-title>
          .
          <source>MAYA Design</source>
          , University of Pittsburgh,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          5.
          <string-name>
            <surname>Schlaefer</surname>
          </string-name>
          , N.:
          <article-title>Deploying Semantic Resources for Open Domain Question Answering</article-title>
          .
          <source>Diploma Thesis</source>
          . Language Technologies Institute School of Computer Science Carnegie Mellon University,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          6.
          <string-name>
            <surname>Metzler</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Indri Retrieval Model Overview</article-title>
          . Available at the Internet: http://ciir.cs.umass.edu/ ~metzler/indriretmodel.html.
          <source>Retrieved in April</source>
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          7.
          <string-name>
            <surname>Gómez</surname>
            ,
            <given-names>J. M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Buscaldi</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rosso</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Sanchis</surname>
          </string-name>
          , E.:
          <article-title>JIRS Languageindependent Passage Retrieval system: A comparative study</article-title>
          .
          <source>In: Proc. 5th int. conf. on natural language processing (ICON)</source>
          , Hyderabad, India,
          <fpage>4</fpage>
          -
          <lpage>6</lpage>
          January
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          8.
          <string-name>
            <surname>Kanerva</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kristoferson</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Holst</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Random indexing of text samples for Latent Semantic Analysis</article-title>
          . In:
          <string-name>
            <given-names>L.R.</given-names>
            <surname>Gleitman</surname>
          </string-name>
          and
          <string-name>
            <surname>A.K.</surname>
          </string-name>
          Josh (eds.),
          <source>Proc. 22nd Annual Conference of the Cognitive Science Society (U Pennsylvania)</source>
          , p.
          <fpage>1036</fpage>
          .
          <string-name>
            <surname>Mahwah</surname>
          </string-name>
          , New Jersey: Erlbaum,
          <year>2000</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          9.
          <string-name>
            <surname>Broder</surname>
            ,
            <given-names>A. Z.</given-names>
          </string-name>
          :
          <article-title>On the resemblance and containment of documents</article-title>
          .
          <source>In: Compression and Complexity of Sequences, IEEE Computer Society</source>
          ,
          <year>1998</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          10.
          <string-name>
            <surname>Lyon</surname>
          </string-name>
          et al.:
          <article-title>Detecting short passages of similar text in large document collections</article-title>
          .
          <source>In: Conference on Empirical Methods in Natural Language (EMNLP2001)</source>
          . pp.
          <fpage>118</fpage>
          -
          <lpage>125</lpage>
          ,
          <year>2001</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          11.
          <string-name>
            <surname>Correa</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Buscaldi</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rossio</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>NLEL-MAAT at CLEF-ResPubliQA</article-title>
          . In: Working Notes ResPubliQA
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          12.
          <string-name>
            <surname>Lopez</surname>
          </string-name>
          ,
          <string-name>
            <surname>Vanessa</surname>
          </string-name>
          , et. al.:
          <article-title>AquaLog: An Ontology-Portable Question Answering System for the Semantic Web</article-title>
          .
          <source>In: ESWC (European Semantic Web Conference) LNCS (Lecture Notes on Computer Science) 3532</source>
          , pp.
          <fpage>546</fpage>
          -
          <lpage>562</lpage>
          . SpringerVerlag Berlin Heidelberg,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          13.
          <string-name>
            <surname>Ittycheriah</surname>
          </string-name>
          ,
          <string-name>
            <surname>Abraham</surname>
          </string-name>
          , et. al.:
          <article-title>IBM's Statistical Question Answering System</article-title>
          .
          <source>In: Proceedings of the 10th Text Retrieval Conference (TREC)</source>
          ,
          <year>2001</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          14.
          <string-name>
            <surname>Metzler</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Croft</surname>
          </string-name>
          . W. Bruce:
          <article-title>Analysis of Statistical Question Classification for Fact-based Questions</article-title>
          . Kluwer Academic Publisher,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          15.
          <string-name>
            <surname>Narayanan</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Harabagiu</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <source>Question Answering Based on Semantic Structures</source>
          ,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          16.
          <string-name>
            <surname>Harabagiu</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          , et. al.:
          <article-title>Employing Two Question Answering Systems in TREC2005</article-title>
          .
          <source>In: Proceedings of the 14th Text Retrieval Conference (TREC)</source>
          ,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          17.
          <string-name>
            <surname>Bos</surname>
          </string-name>
          , J.:
          <source>The “La Sapienza” Question Answering System at TREC-2006. In: Proceedings of the 15th Text Retrieval Conference (TREC)</source>
          ,
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          18.
          <string-name>
            <surname>Glöckner</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Pelzer</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>The LogAnswer Project at CLEF 2009</article-title>
          . In: Working Notes ResPubliQA
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          19.
          <string-name>
            <surname>Andrenucci</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Sneiders</surname>
          </string-name>
          , E.: Automated Question Answering:
          <article-title>Review of the Main Approaches</article-title>
          .
          <source>In: Proceedings of the Third International Conference on Information Technology and Applications (ICITA) IEEE Computer Society</source>
          ,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          20.
          <string-name>
            <surname>Bilotti</surname>
            ,
            <given-names>Matthew W.</given-names>
          </string-name>
          &amp;
          <string-name>
            <surname>Nyberg</surname>
          </string-name>
          , Eric.:
          <article-title>Improving Text Retrieval Precision and Answer Accuracy in Question Answering Systems</article-title>
          .
          <source>In: Proceedings of the ACL 2nd Workshop on Information Retrieval for Question Answering</source>
          ,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          21.
          <string-name>
            <surname>Peñas</surname>
          </string-name>
          ,
          <string-name>
            <surname>Anselmo</surname>
          </string-name>
          , et. al.:
          <source>Overview of ResPubliQA</source>
          <year>2009</year>
          :
          <article-title>Question Answering Evaluation over European Legislation</article-title>
          .
          <source>Cross Language Evaluation Forum</source>
          ,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>