<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">A logic programming based approach to the QA@CLEF05 track</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Paulo</forename><surname>Quaresma</surname></persName>
							<affiliation key="aff0">
								<orgName type="department">Departamento de Informátiva</orgName>
								<orgName type="institution">Universidade de Évora</orgName>
								<address>
									<country key="PT">Portugal</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Irene</forename><surname>Rodrigues</surname></persName>
							<affiliation key="aff0">
								<orgName type="department">Departamento de Informátiva</orgName>
								<orgName type="institution">Universidade de Évora</orgName>
								<address>
									<country key="PT">Portugal</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">A logic programming based approach to the QA@CLEF05 track</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">143735A497DFF8367116399AAE3945EB</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-25T00:37+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>H.3 [Information Storage and Retrieval]: H.3.1 Content Analysis and Indexing</term>
					<term>H.3.3 Information Search and Retrieval</term>
					<term>H.3.4 Systems and Software Measurement, Performance, Experimentation, Algorithms Question answering, NLP, Prolog</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>In this paper the methodology followed to build a question-answering system for the Portuguese language is described. The system has two modules: preliminary analysis of documents (information extraction) and query processing (information retrieval). The proposed approach is based on computational linguistic theories: syntactical analysis (constraint grammars); followed by semantic analysis using the discourse representation theory; and, finally, a semantic/pragmatic interpretation using ontologies and logical inference.</p><p>The system was evaluated under the CLEF'05 question and answering track with a collection of documents from two newspapers: Público (Portuguese) and Folha de São Paulo (Brazilian).</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">Introduction</head><p>This paper describes an ongoing project at the Informatics Department of the University of Évora, Portugal, aiming to develop a question answering system for the Portuguese language.</p><p>The system has two modules: preliminary analysis of documents (information extraction) and query processing (information retrieval).</p><p>The analysis of the document collection and queries is done using models from computational linguistic theories. This processing includes: syntactical analysis of sentences using the constraint grammar Palavras <ref type="bibr" target="#b2">[3]</ref>; semantical analysis using discourse representation theory <ref type="bibr" target="#b5">[5]</ref>; and, finally, semantic/pragmatic interpretation using ontologies and logical inference.</p><p>Knowledge representation and ontologies are handled through the use of an extension to PRO-LOG, ISCO <ref type="bibr" target="#b0">[1,</ref><ref type="bibr" target="#b1">2]</ref>, which allows to integrate logic programming and external databases. In this way it is possible to solve scalability problems like the need to represent more than 10 millions of discourse entities.</p><p>The QA system, in order to satisfy CLEF requirements, should be able to answer queries in natural language, based on information conveyed by a collection of documents. The answer to a specific question is: a set of words and the identification of the document and sentence, which was used as the source of information. For instance, for the following question:</p><p>Who is John Lennon's widow?</p><p>Our system answers: Yoko Ono -document: publico/publico95/950807/001 -sentence: 2 At the moment, the system is able to answer questions about:</p><p>• Places:</p><p>Where is Régua?</p><p>• Dates: When was Mr. X arrested?</p><p>• Definitions:</p><p>What is ONU?</p><p>• Specific: How many times was Mr. X accused of being a drug dealer? What crimes as Mr. Y committed? However, the system can also be used to improve other information retrieval tasks:</p><p>• Improve the performance of information retrieval systems, helping to obtain the set of relevant documents.</p><p>Given a query, the system can be used to retrieve all documents having a sentence which verifies the query.</p><p>For the question "Who is John Lennon's widow" our system is able to retrieve all documents having a sentence which verifies the following term:</p><p>∃X, Y : widow(X, Y ), name(X, John Lennon )</p><p>• Help to structure documents in a semi-automatic way.</p><p>The system is able to extract facts from the documents and to give them a structure (accordingly with an ontology).</p><p>The proposed system is an evolution of a previous system evaluated at CLEF 2004 <ref type="bibr" target="#b7">[7]</ref>. Some of the existing problems were solved, namely, the need to use a pre-processing information retrieval engine to decrease the complexity of the problem. In this CLEF edition, we were able to solve this major scalability problem via the use of ISCO and its power to connect PROLOG and relational databases.</p><p>However, the pre-processing of the collection of documents took more time than we expected and we were not able to answer questions to the Folha de S. Paulo newspaper. As we will point out in the evaluation section this was our major problem and it is the reason why our results didn't improve from CLEF04 to CLEF05.</p><p>In the next section the architecture of the system is described. In sections 3 and 4 the syntactical and the semantical modules are described in detail. Section 5 presents the knowledge representation approach. Section 6 describes the semantic-pragmatic interpretation of the documents, based on the previous analysis and on the ontology. Section 7 shows the processing of a query and the generation of the correspondent answer. In section 8 the evaluation results are presented. Finally, in section 9 some conclusions and future work are discussed. The QA system has two main modules:</p><formula xml:id="formula_0">• Information extraction;</formula><p>This module extracts information from the documents and it creates a knowledge base.</p><p>The module, see figure <ref type="figure" target="#fig_0">1</ref>, is composed by several sub-modules:</p><p>-Syntactical analysis: sentences are processed with the Palavras <ref type="bibr" target="#b2">[3]</ref> parser.</p><p>After this phase, a new collection of documents (with the parsing result) is obtained.</p><p>-Semantic analysis: the new collection of sentences in rewritten <ref type="bibr" target="#b5">[5]</ref> creating another collection, where each document has a DRS (structure for the discourse representation), a list of discourse referents and a set of conditions.</p><p>-Semantic and pragmatic interpretation: in this phase the previous collection of documents is processed, taking into account an ontology and, as a result, a knowledge base is built. This knowledge base contains instances of the ontology.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>• Information retrieval</head><p>This module processes the query and it generates the answer: a set of words and the identification of the document and sentence where the answer was found.  -Syntactical analysis: using the parser Palavras <ref type="bibr" target="#b2">[3]</ref>.</p><p>-Semantic analysis: from the parser output, a discourse structure is built, a DRS <ref type="bibr" target="#b5">[5]</ref> with the correspondent referents.</p><p>-Semantic/Pragmatic interpretation: in this phase, some conditions are rewritten, taking into account the ontology, and generating a new DRS.</p><p>-Query Processing: the final query representation is interpreted in the knowledge base through the unification of the discourse entities of the query with documents discourse entities (see section 7).</p><p>In the next sections these sub-modules are described in more detail.</p><p>Syntactical analysis is obtained through the use of the PALAVRAS parser from Eckhard Bick <ref type="bibr" target="#b2">[3]</ref>, developed in the context of the VISL 1 project at the University of Southern Denmark. This parser gives good morpho-syntactical information and it has a god coverage of the Portuguese language. For instance, in our system the verb lemma (infinitive form) is used as the name of the predicates in the semantic analysis.</p><p>As an example, consider the following sentence (3.1):</p><p>Um patologista defendeu que Jimi Hendrix morreu de asfixia após ter ingerido álcool e uma dose excessiva de barbitúricos. (3.1)</p><p>"A pathologist argued that Jimi Hendrix died of asphyxia after drinking alcoholic beverages and an excessive dose of barbiturics".</p><p>The syntactical structure of this sentence is the following: </p><formula xml:id="formula_1">STA:fcl =SUBJ:np ==&gt;N:art( um M S &lt;arti&gt;) Um ==H:n( patologista M S &lt;Hprof&gt;) patologista =P:v-fin( defender PS 3S IND) defendeu =ACC:fcl ==SUB:conj-s( que ) que ==SUBJ:prop( Jimi_Hendrix M/F S) Jimi_Hendrix ==P:v-</formula><formula xml:id="formula_2">) ) ) ) ) ) ).</formula></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4">Semantic analysis</head><p>The semantic analysis rewrites the syntactical structure in to a discourse representation structure <ref type="bibr" target="#b5">[5]</ref>, DRS. At present, we only deal with factual sentences, i.e., sentences with existential quantification over the discourse entities. So, our discourse structures are sets of referents, existentially quantified variables, and sets of conditions, first order predicates.</p><p>Each syntactical tree, represented in Prolog, is rewritten accordingly with a set of rules and integrated in a DRS.</p><p>In order to allow alternative interpretations, the link between prepositional phrases in done using the relation rel with 3 arguments, the preposition and two discourse entities. This predicate rel allows the semantic/pragmatic interpretation to infer the adequate connection between the referents. For instance, the sentence 'O dono do cão'/'The owner of the dog', is represented by the following DRS: drs( entities:[ A:(def, male, sing), B:(def, male, sing)], conditions:[owner(A), dog(B), rel(of,A,B)] )</p><p>As it can be seen in the next section, this representation allows the semantic/pragmatic interpretation to rewrite the DRS, obtaining the following structure: This representation is obtained because "Como/How" is interpreted as "de que/of what". In the semantic-pragmatic interpretation and in the query processing phase, the structure (4.1) might unify with sentence (3.1) and we may obtain the following answer: "Jimi Hendrix died of asphyxia".</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5">Ontology and knowledge representation</head><p>In order to represent the ontology and the extracted facts, we use an extension to logic programming, ISCO <ref type="bibr" target="#b0">[1,</ref><ref type="bibr" target="#b1">2]</ref>, which allows Prolog to access databases. This technology is fundamental to our system because we have a very large database of referents: more than 9 millions only for the Público newspaper.</p><p>Databases are defined in ISCO from ontologies. Our system uses two different ontologies:</p><p>• one ontology built by us aiming to model common knowledge, such as, geography (mainly places), and dates;</p><p>This kind of knowledge is important to correctly extract facts from the documents and to be able to answer questions about places. The ontology defines places (cities, countries, . . . ) and relations between places.</p><p>• one ontology generated automatically from the document collection <ref type="bibr" target="#b9">[9,</ref><ref type="bibr" target="#b8">8]</ref>;</p><p>This ontology, although being very simple, allows the representation of the domain knowledge.</p><p>The ontology can be defined directly in ISCO or in OWL (Ontology Web Language) and transformed in ISCO <ref type="bibr" target="#b8">[8]</ref>.</p><p>The knowledge extraction module identifies facts (instances of an ontology classes) and inserts them as rows in a database table.</p><p>For instance, sentence (3.1), with semantic representation in page 7, would generate several tuples in the database. First order logical expressions are skolemized, i.e., each variable existentially quantified is replaced by a different identifier:</p><formula xml:id="formula_3">• (123,''Jimmy Hendrix'') is added to table name • (123) is added to table die • (124) is added to table asphyxia • rel(de,123,124) is added to table rel</formula><p>In the document processing phase, our system uses the first sentence interpretation (note that for each sentence there might exist several distinct interpretations). This is caused by temporal and spacial complexity problems but it does not seem to decrease much the performance of the system. Nevertheless, additional measures should be done in order to fully evaluate the impact of this option.</p><p>Additionally, we also add information in the database linking referents with the documents and sentences were they appeared. For instance the tuple (123,'publico/publico95/950605/005',4) would be added to table referred in.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6">Semantic/Pragmatic Interpretation</head><p>Semantic/pragmatic interpretation tries to reinterpret semantical information, taking into account the considered ontology.</p><p>This process receives as input a discourse representation structure, DRS, and it interprets it using rules obtained from the knowledge ontology and the information in the database.</p><p>In order to obtain a good interpretation, our strategy is to search for the best explanation that supports the sentence logical form. This strategy for pragmatic interpretation was initially proposed by <ref type="bibr" target="#b3">[4]</ref>.</p><p>The knowledge base for the pragmatic interpretation is built from the ontology description in ISCO. The inference in the knowledge base uses abduction and finite domain constraint solvers.</p><p>Suppose the following sentence:</p><p>"A. conduz com uma taxa de alcoolemia de 2.15." "A. drives with an alcoholic rate of 2.15.".</p><p>which, by the semantic analysis, is transformed into the following structure: one DRS, four discourse referents, and a set of conditions: drs( entities:[A:(def,male,sing), B:(indef,fem,sing), C:(indef,fem,sing), D:(def,male,sing)] conditions:[name(A, 'A.'), drive(A), rel(with,A,B),</p><p>The semantic/pragmatic interpretation process, using information from the ontology, will rewrite the DRS into the following one: drs( entities:[A:(def,male,sing), B:(def,male,sing)] conditions:[name(A, 'A.'), person(A), drive(A,_,_,_,B), alcohol\_rate(B,2,15)] )</p><p>The interpretation of rel(with,A,B) as drive( <ref type="figure">A, , , ,B</ref>) is possible because the ontology has a class drive, which relates persons driving in a time interval with a alcoholic rate in blood.</p><p>One of the major problems of this phase is to correctly identify the distinct referents in the documents. It is important to use the same skolem constant to identify the same referent but, in any situation, different individuals should have the same identifier (skolem constant).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="7">Answer generation</head><p>The generation of the answer is done in two steps:</p><p>1. identification of the database referent that unifies with the referent of the interrogative pronoun in the question.</p><p>2. retrieval of the referent properties and generation of the answer.</p><p>In order to illustrate this process, suppose the following question:</p><p>"Quem cometeu um homicídio por conduzir alcoolizado?" "Who committed an homicide because he/she was driving drunk?"</p><p>This question is represent by the following DRS, after syntactical and semantical analysis:</p><p>drs( entities:[A:(who,male/fem,sing), B:(indef,male,sing), C:(indef,male,sing)], conditions:[committed(A,B), homicide(B), rel(because,A,C), drunk(C), drive(C)] )</p><p>The semantic/pragmatic interpretation of this question is done using the ontology of concepts and it allows to obtain the following DRS: drs( entities:[A:(who,male/fem,sing), B:(indef,male/fem,sing/plu), C:(def,fem,sing), conditions:[homicide(A,B), person(A), person(B), drive(A,_,_,_,C), alcohol\_rate(C),C&gt;0.5] )</p><p>• In order to perform the first step of the answer generation:</p><p>We keep the referent variables of the question and we try to prove the conditions of the DRS in the knowledge base. If the conditions can be satisfied in the knowledge base, the discourse referents are unified with the identifiers (skolem constants) of the individuals.</p><p>• The next step is to retrieve the words that constitute the answer:</p><p>In this phase we should retrieve the conditions about the identified referent A and choose which ones better characterize the entity. Our first option is to choose a condition with the predicate name (name(A,Name)). However, it is not always simple to find the adequate answer to a question. See, for instance, the following questions:</p><p>-What crimes committed X? -How many habitants has Kalininegrado?</p><p>-What is the nationality of Miss Universe? -Who is Flavio Briatore?</p><p>In order to choose the best answer to a question our systems has an algorithm which takes into account the syntactical category of the words that may appear in the answer and it tries to avoid answers with words that appear in the question.</p><p>Questions about places or dates have a special treatment involving the access to a database of places or dates.</p><p>Note that several answers may exist for a specific question. In CLEF05 we decided to calculate all possible answers and to choose the most frequent one.</p><p>CLEF05 also imposes that the answer is supported by a single sentence in a specific document. Our system is able to obtain answers with conditions in several documents but we constrained the system to obtain only answers with referents introduced in the same sentence (predicate referred in allows to obtain that information -see page 8).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="8">Evaluation</head><p>The evaluation of our system was performed in the context of CLEF -Cross Language Evaluation Forum -2005. In this forum a set (200) of questions is elaborated by a jury and given to the system. The system's answers are, then, evaluated by the same jury.</p><p>Our system had the following results:</p><p>• 25% of correct answers (50 answers).</p><p>• 1.5% correct but unsupported answers (3 answers).</p><p>• 11% inexact answers -too many (or too few) words (22 answers).</p><p>• 62.5% wrong answers (125 answers).</p><p>The system had 125 wrong answers, but it is important to point out that 105 of these wrong answers were NIL answers, i.e., situations were the system was not able to find any answer to the questions. So, only in 10% of the situations (20 answers) our system gave a really wrong answer.</p><p>The major problem with the remaining 105 no-answers is the fact that, due to time constraints we were not able to process the collection of documents from the Folha de S. Paulo newspaper. At present, we do not know how many of these no-answers would be answered by this collection, but we expect our results to improve significatively.</p><p>A preliminary analysis of the other incorrect answers showed that the main cause of problems in our system is related with lack of knowledge: wrong syntactical analysis; lack of synonyms; and, mostly, an incomplete ontology. In fact, most problems are related with incorrect pragmatic analysis due to an incomplete ontology.</p><p>However, and taking into account that our answers were computed using only one collection of documents (the Público newspaper), and comparing with the CLEF2004 results, we believe our system produced good and promising results. In fact, it showed to have a quite good precision on the non NIL answers: only 10% of these answers were wrong.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="9">Conclusions and Future Work</head><p>We propose an architecture for a question answering system for the Portuguese language.</p><p>Our system uses natural language processing techniques to create a knowledge base with the information conveyed by documents. Queries are analysed by the same tools and logical inferences over the knowledge base are performed, trying to find an adequated answer. The inference process is performed using a logic programming framework and the Prolog inference engine.</p><p>The system main problems are related with errors in the several NLP tools and with the lack of coverage of the ontology.</p><p>At present, we are re-evaluating our system using a knowledge base with the two newspaper collection. We expect our results to improve significatively.</p><p>As future work, we intend to explore the problem of automatically build ontologies. The improvement of the used NLP tools is another area needing much work. We also intend to handle anaphoric relations in the documents, allowing the reduction of the number of distinct referents.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1</head><label>1</label><figDesc>Figure 1: Document Processing</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure 2 :Figure 2</head><label>22</label><figDesc>Figure 2: Query Processing</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head></head><label></label><figDesc>drs(entities:[ A:(def, male, sing), B:(def, male, sing)], conditions:[belongs(A,B), person(A), dog(B)] )In order to show an example of a syntactical tree transformation into a DRS, we show sentence(3.1)  rewritten : drs (entities:[ A: (indef, male, sing), B: (def, male/fem, sing), C: (def, fem, sing), D: (def, male, sing), E: (indef, fem, sing) ], condições:[ pathologist (A), argue(A,B), name(B, 'Jimmy Hendrix'), died(B), rel (of, B, C), asphyxia(C), rel (after, C, D), drinking(D), alcohol(D), dose(D), excessive(D), rel(of, D, E), barbiturics(E)]) User queries are also interpreted and rewritten into DRS. For instance, the question: Como morreu Jimi Hendrix?/How did Jimi Hendrix died? (4.1) is transformed into the following discourse structure: drs( entities:[F:(def, male/fem, sing), G: interrog(que), male, sing] conditions:[died(F), name(F,'Jimmy Hendrix'), rel(of,F,G)] )</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_1"><head></head><label></label><figDesc>This structure is transformed by our system in a equivalent Prolog representation, which will be used as the input of the semantic analyser.</figDesc><table><row><cell>sta(fcl,</cell></row><row><cell>subj(np,</cell></row><row><cell>n(art('um',</cell></row><row><cell>'M', 'S', &lt;arti&gt; ), 'Um'),</cell></row><row><cell>h(n('patologista',</cell></row><row><cell>'M', 'S', &lt;Hprof&gt; ),</cell></row><row><cell>'patologista')),</cell></row><row><cell>p(v_fin('defender', 'PS', '3S', 'IND'),</cell></row><row><cell>'defendeu'),</cell></row><row><cell>acc(fcl,</cell></row><row><cell>sub(</cell></row><row><cell>conj_s('que'), 'que')),</cell></row><row><cell>subj(prop('Jimi_Hendrix', 'M/F', 'S'),</cell></row><row><cell>'Jimi_Hendrix'),</cell></row><row><cell>p(v_fin('morrer', 'PS', '3S', 'IND'),</cell></row><row><cell>'morreu'),</cell></row><row><cell>piv(pp,</cell></row><row><cell>h(prp('de'),'de'),</cell></row><row><cell>p(np,</cell></row><row><cell>h(n('asfixia','F','S', &lt;sick&gt; ), 'asfixia'),</cell></row><row><cell>n(pp,</cell></row><row><cell>h(prp('após'), 'após'),</cell></row><row><cell>p(icl,</cell></row><row><cell>p(vp,</cell></row><row><cell>aux(v_inf('ter'),'ter'),</cell></row><row><cell>mv(v_pcp('ingerir'), 'ingerido')),</cell></row><row><cell>acc(n(´álcool', fin( morrer PS 3S IND) morreu 'M', 'S', &lt;cm-liq&gt; ), ´álcool'), ==PIV:pp co(conj_c('e'), 'e'), ===H:prp( de ) de acc(np, ===P&lt;:np n(art('um', ====H:n( asfixia F S &lt;sick&gt;) asfixia 'F','S',&lt;arti&gt;), 'uma'), ====N&lt;:pp h(n('dose','F','S'), 'dose'), =====H:prp( após ) após n(adj('excessivo', =====P&lt;:icl 'F','S'), 'excessiva'), ======P:vp n(pp, =======AUX:v-inf( ter ) ter h(prp('de'),'de'), =======MV:v-pcp( ingerir ) ingerido p(n('barbitúrico', ======ACC:n( álcool M S &lt;cm-liq&gt;) álcool 'M','P'), 'barbitúricos' , '.' )</cell></row><row><cell>======CO:conj-c( e ) e</cell></row><row><cell>======ACC:np</cell></row><row><cell>=======&gt;N:art( um F S &lt;arti&gt;) uma</cell></row><row><cell>=======H:n( dose F S) dose</cell></row><row><cell>=======N&lt;:adj( excessivo F S)</cell></row><row><cell>excessiva</cell></row><row><cell>=======N&lt;:pp</cell></row><row><cell>========H:prp( de ) de</cell></row><row><cell>========P&lt;:n( barbitúrico M P)</cell></row><row><cell>barbitúricos</cell></row></table></figure>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Isco: A practical language for heterogeneous information system construction</title>
		<author>
			<persName><forename type="first">Salvador</forename><surname>Abreu</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of INAP&apos;01</title>
				<meeting>INAP&apos;01<address><addrLine>Tokyo, Japan</addrLine></address></meeting>
		<imprint>
			<publisher>INAP</publisher>
			<date type="published" when="2001-10">October 2001</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">A dialogue manager for accessing databases</title>
		<author>
			<persName><forename type="first">Salvador</forename><surname>Abreu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Paulo</forename><surname>Quaresma</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Luis</forename><surname>Quintano</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Irene</forename><surname>Rodrigues</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">13th European-Japanese Conference on Information Modelling and Knowledge Bases</title>
				<meeting><address><addrLine>Kitakyushu, Japan</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2003-06">June 2003</date>
			<biblScope unit="page" from="213" to="224" />
		</imprint>
		<respStmt>
			<orgName>Kyushu Institute of Technology</orgName>
		</respStmt>
	</monogr>
	<note>To be published by IOS Press</note>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">The Parsing System &quot;Palavras</title>
		<author>
			<persName><forename type="first">Eckhard</forename><surname>Bick</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Automatic Grammatical Analysis of Portuguese in a Constraint Grammar Framework</title>
				<imprint>
			<publisher>Aarhus University Press</publisher>
			<date type="published" when="2000">2000</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<title level="m" type="main">Interpretation as abduction</title>
		<author>
			<persName><forename type="first">Jerry</forename><surname>Hobbs</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Mark</forename><surname>Stickel</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Douglas</forename><surname>Appelt</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Paul</forename><surname>Martin</surname></persName>
		</author>
		<imprint>
			<biblScope unit="volume">499</biblScope>
			<biblScope unit="page">333</biblScope>
		</imprint>
	</monogr>
	<note type="report_type">Technical Report SRI Technical Note</note>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<title/>
		<author>
			<persName><forename type="first">Ravenswood</forename><surname>Ave</surname></persName>
		</author>
		<imprint>
			<date type="published" when="1990">94025. 1990</date>
			<pubPlace>Menlo Park, CA</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<monogr>
		<title level="m" type="main">From Discourse to Logic:An Introduction to Modeltheoretic Semantics of Natural Language, Formal Logic and Discourse Representation Theory</title>
		<author>
			<persName><forename type="first">Hans</forename><surname>Kamp</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Uwe</forename><surname>Reyle</surname></persName>
		</author>
		<imprint>
			<date type="published" when="1993">1993</date>
			<publisher>D. Reidel</publisher>
			<pubPlace>Dordrecht</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Interrogating legal documents: The future of legal information systems?</title>
		<author>
			<persName><forename type="first">M-F</forename><surname>Moens</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the JURIX 2003 Workshop on Question Answering for Interrogating Legal Documents</title>
				<meeting>the JURIX 2003 Workshop on Question Answering for Interrogating Legal Documents<address><addrLine>Utrecht, Netherlands</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2003">2003</date>
			<biblScope unit="page" from="19" to="30" />
		</imprint>
		<respStmt>
			<orgName>Utrecht University</orgName>
		</respStmt>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Using dialogues to access semantic knowledge in a web legal IR system</title>
		<author>
			<persName><forename type="first">Paulo</forename><surname>Quaresma</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Irene</forename><surname>Rodrigues</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Procs. of the Workshop on Question Answering for Interrogating Legal Documents of JURIX&apos;03 -The 16th Annual Conference on Legal Knowledge and Information Systems</title>
				<editor>
			<persName><forename type="first">Marie-Francine</forename><surname>Moens</surname></persName>
		</editor>
		<meeting>s. of the Workshop on Question Answering for Interrogating Legal Documents of JURIX&apos;03 -The 16th Annual Conference on Legal Knowledge and Information Systems<address><addrLine>Utrecht, Netherlands</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2003-12">December 2003</date>
		</imprint>
		<respStmt>
			<orgName>Utrecht University</orgName>
		</respStmt>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<monogr>
		<title level="m" type="main">Uma metodologia para a construção automática de ontologias e a sua aplicação em sistemas de recuperação de informação -a methodology for the automatic creation of ontologies and its application in information retrieval systems</title>
		<author>
			<persName><forename type="first">José</forename><surname>Saias</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2003">2003</date>
		</imprint>
		<respStmt>
			<orgName>University of Évora, Portugal</orgName>
		</respStmt>
	</monogr>
	<note type="report_type">Master&apos;s thesis</note>
	<note>In Portuguese</note>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Using nlp techniques to create legal ontologies in a logic programming based web information retrieval system</title>
		<author>
			<persName><forename type="first">José</forename><surname>Saias</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Paulo</forename><surname>Quaresma</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Workshop on Legal Ontologies and Web based legal information management of the 9th International Conference on Artificial Intelligence and Law</title>
				<meeting><address><addrLine>Edinburgh, Scotland</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2003-06">June 2003</date>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
