<?xml version="1.0"?><!DOCTYPE article SYSTEM "/project/take/software/searchbench_offline_processing/paperxml_generator/aclextractor/src/python/../resource/dtd/paperxml.dtd"><article><header><firstpageheader><page local="1"/><title>Learning Domain Ontologies from Document Warehouses and Dedicated Web Sites</title><pubinfo>(c 2004 Association for Computational Linguistics</pubinfo><author surname="Navigli" givenname="Roberto"><org  name='Universita di Roma "La Sapienza'/></author><author surname="Velardi" givenname="Paola"><org  name='Universita di Roma "La Sapienza'/></author></firstpageheader><frontmatter><p><b>Learning Domain Ontologies from Document Warehouses and Dedicated Web Sites</b></p><p>Roberto Navigli*</p><p>Universita di Roma "La Sapienza"</p><p>Paola Velardi</p></frontmatter><abstract><i>We present a method and a tool, OntoLearn, aimed at the extraction of domain ontologies from Web sites, and more generally from documents shared among the members ofvirtual organiza­tions. OntoLearn first extracts a domain terminology from available documents. Then, complex domain terms are semantically interpreted and arranged in a hierarchical fashion. Finally, a general-purpose ontology, WordNet, is trimmed and enriched with the detected domain concepts. The major novel aspect ofthis approach is semantic interpretation, that is, the association ofa complex </i>concept <i>with a complex </i>term. <i>This involves finding the appropriate WordNet concept for each word of a terminological string and the appropriate conceptual relations that hold among the concept components. Semantic interpretation is based on a new word sense disambiguation algorithm, called structural semantic interconnections.</i> </abstract></header><body><section number="1." title="Introduction"><p>The importance of domain ontologies is widely recognized, particularly in relation to the expected advent of the Semantic Web (Berners-Lee 1999). The goal of a domain on­tology is to reduce (or eliminate) the conceptual and terminological confusion among the members of a virtual community of users (for example, tourist operators, commer­cial enterprises, medical practitioners) who need to share electronic documents and information of various kinds. This is achieved by identifying and properly defining a set of relevant concepts that characterize a given application domain. An ontology is therefore a shared understanding of some domain of interest (Uschold and Gruninger 1996). The construction of a shared understanding, that is, a unifying conceptual frame­work, fosters• communication and cooperation among people</p><p>• better enterprise organization</p><p>• interoperability among systems</p><p>• system engineering benefits (reusability, reliability, and specification)</p><p>Creating ontologies is, however, a difficult and time-consuming process that involves specialists from several fields. Philosophical ontologists and artificial intelligence lo­gicians are usually involved in the task of defining the basic kinds and structures of concepts (objects, properties, relations, and axioms) that are applicable in every</p><p>* Dipartimento di Informatica, Universita di Roma "La Sapienza," Via Salaria, 11S - 00198 Roma, Italia. E-mail: {navigli, velardi}@di.uniroma1.it.</p><page local="2" global="152"/><p>Foundational Ontology</p><p>Core Ontology</p><p>Specific Domain Ontology</p><p><b>Figure 1</b></p><p>The three levels of generality of a domain ontology.</p><p>possible domain. The issue of identifying these very few "basic" principles, now often referred to as <b>foundational ontologies </b>(FOs) (or top, or upper ontologies; see Figure 1) (Gangemi et al. 2002), meets the practical need of a model that has as much generality as possible, to ensure reusability across different domains (Smith and Welty 2001).</p><p>Domain modelers and knowledge engineers are involved in the task of identify­ing the key domain conceptualizations and describing them according to the organi­zational backbones established by the foundational ontology. The result of this effort is referred to as the <b>core ontology </b>(CO), which usually includes a few hundred ap­plication domain concepts. While many ontology projects eventually succeed in the task of defining a core ontology,<footnote anchor="1"/> populating the third level, which we call the <b>specific domain ontology </b>(SDO), is the actual barrier that very few projects have been able to overcome (e.g., WordNet [Fellbaum 1995], Cyc [Lenat 1993], and EDR [Yokoi 1993]), but they pay a price for this inability in terms of inconsistencies and limitations.<footnote anchor="2"/></p><p>It turns out that, although domain ontologies are recognized as crucial resources for the Semantic Web, in practice they are not available and when available, they are rarely used outside specific research environments.</p><p>So which features are most needed to build usable ontologies?</p><p>• Coverage: The domain concepts <u>must be there;</u> the SDO must be sufficiently (for the application purposes) populated. Tools are needed to extensively support the task of identifying the relevant concepts and the relations among them.</p><p>• Consensus: Decision making is a difficult activity for one person, and it gets even harder when a group of people must reach consensus on a given issue and, in addition, the group is geographically dispersed. When a group of enterprises decide to cooperate in a given domain, they have first to agree on many basic issues; that is, they must reach a <u>consensus</u> of the business domain. Such a common view must be reflected by the domain ontology.</p><p>• Accessibility: The ontology must be easily <u>accessible</u>: tools are needed to easily integrate the ontology within an application that may clearly show</p><p>1 Several ontologies are already available on the Internet, including a few hundred more or less extensively defined concepts.</p><p>2 For example, it has been claimed by several researchers (e.g., Oltramari et al., 2002) that in WordNet there is no clear separation between concept-synsets, instance-synsets, relation-synsets, and meta-property-synsets.</p><page local="3" global="153"/><p>its decisive contribution, e.g., improving the ability to share and exchange information through the web.</p><p>In cooperation with another research institution,<footnote anchor="3"/> we defined a general architecture and a battery of systems to foster the creation of such "usable" ontologies. Consensus is achieved in both an implicit and an explicit way: implicit, since candidate concepts are selected from among the terms that are frequently and consistently employed in the documents produced by the virtual community of users; explicit, through the use of Web-based groupware aimed at consensual construction and maintenance of an ontology. Within this framework, the proposed tools are <b>OntoLearn, </b>for the automatic extraction of domain concepts from thematic Web sites; <b>ConSys, </b>for the validation of the extracted concepts; and <b>SymOntoX, </b>the ontology management system. This ontology-learning architecture has been implemented and is being tested in the con­text of several European projects,<footnote anchor="4"/> aimed at improving interoperability for networked enterprises.</p><p>In Section 2, we provide an overview of the complete ontology-engineering archi­tecture. In the remaining sections, we describe in more detail OntoLearn, a system that uses text mining techniques and existing linguistic resources, such as WordNet and SemCor, to learn, from available document warehouses and dedicated Web sites, do­main concepts and taxonomic relations among them. OntoLearn automatically builds a specific domain ontology that can be used to create a specialized view of an exist­ing general-purpose ontology, like WordNet, or to populate the lower levels of a core ontology, if available.</p></section><section number="2." title="The Ontology Engineering Architecture"><p>Figure 2 reports the proposed ontology-engineering method, that is, the sequence of steps and the intermediate outputs that are produced in building a domain ontol­ogy. As shown in the figure, ontology engineering is an iterative process involving concept learning (OntoLearn), machine-supported concept <u>validation</u> (ConSys), and management (SymOntoX).</p><p>The engineering process starts with OntoLearn exploring available documents and related Web sites to learn domain concepts and detect taxonomic relations among them, producing as output a domain concept forest. Initially, we base concept learning on external, generic knowledge sources (we use WordNet and SemCor). In subsequent cycles, the domain ontology receives progressively more use as it becomes adequately populated.</p><p>Ontology validation is undertaken with ConSys (Missikoff and Wang 2001), a Web-based groupware package that performs consensus building by means of thor­ough validation by the representatives of the communities active in the application domain. Throughout the cycle, OntoLearn operates in connection with the ontology management system, SymOntoX (Formica and Missikoff 2003). Ontology engineers use this management system to define and update concepts and their mutual connections, thus allowing the construction of a semantic net. Further, SymOntoX's environment can attach the automatically learned domain concept trees to the appropriate nodes of the core ontology, thereby enriching concepts with additional information. SymOntoX</p><p>3 The LEKS-CNR laboratory in Rome.</p><p>4 The Fetish EC project, ITS-13015 (http://fetish.singladura.com/index.php) and the Harmonise EC project, IST-2000-29329 (http://dbs.cordis.lu), both in the tourism domain, and the INTEROP Network of Excellence on interoperability IST-2003-508011.</p><page local="4" global="154"/><p><b>Figure 2</b></p><p>The ontology-engineering chain.</p><p>also performs consistency checks. The self-learning cycle in Figure 2 consists, then, of two steps: first, domain users and experts use ConSys to validate the automatically learned ontology and forward their suggestions to the knowledge engineers, who im­plement them as updates to SymOntoX. Then, the updated domain ontology is used by OntoLearn to learn new concepts from new documents.</p><p>The focus of this article is the description of the OntoLearn system. Details on other modules of the ontology-engineering architecture can be found in the referenced papers.</p></section><section number="3." title="Architecture of the OntoLearn System"><p>Figure 3 shows the architecture of the OntoLearn system. There are three main phases: First, a domain terminology is <u>extracted</u> from available texts in the application domain (specialized Web sites and warehouses, or documents exchanged among members of a virtual community), and <u>filtered</u> using natural language processing and statistical techniques. Second, terms are semantically interpreted (in a sense that we clarify in Section 3.2) and ordered according to <u>taxonomic relations,</u> generating a <b>domain con­cept forest </b>(DCF). Third, the DCF is used to update the existing ontology (WordNet or any available domain ontology).</p><p>In a "stand-alone" mode, OntoLearn automatically creates a specialized view of WordNet, pruning certain generic concepts and adding new domain concepts. When used within the engineering chain shown in Figure 2, ontology integration and up­dating is performed by the ontology engineers, who update an existing core ontology using SymOntoX.</p><p>In this article we describe the stand-alone procedure.</p><subsection number="3.1" title="Phase 1: Terminology Extraction"><p>Terminology is the set of words or word strings that convey a single (possibly complex) meaning within a given community. In a sense, terminology is the surface appearance, in texts, of the domain knowledge of a community. Because of their low ambiguity and high specificity, these words are also <i>particularly useful for conceptualizing aknowledge domain </i>or for supporting the creation of a domain ontology. Candidate terminological expressions are usually captured with more or less shallow techniques, ranging from stochastic methods (Church and Hanks 1989; Yamamoto and Church 2001) to more sophisticated syntactic approaches (Jacquemin 1997).</p><page local="5" global="155"/><p>domain corpus</p><p>contrastive corpora terminology extraction candidate extraction terminology filtering</p><p>Inductive learner</p><doubt alpha="100.0" length="7" tooSmall="False" monospace="0.0">Natural</doubt><p>Language</p><p>Processor ontology integration and updating</p><doubt alpha="100.0" length="7" tooSmall="False" monospace="0.0">WordNet</doubt><p>Domain Concept Forest</p><p><b>Figure 3</b></p><p>The architecture of OntoLearn.</p><doubt alpha="0.0" length="1" tooSmall="False" monospace="0.0">2</doubt><p>Obviously, richer syntactic information positively influences the quality of the result to be input to the statistical filtering. In our experiments we used the linguis­tic processor ARIOSTO (Basili, Pazienza, and Velardi 1996) and the syntactic parser CHAOS (Basili, Pazienza, and Zanzotto 1998). We parsed the available documents in the application domain in order to extract a list <i>Tc </i>of syntactically <i>plausible </i>termino­logical noun phrases (NPs), for example, compounds <i>(credit card), </i>adjective-NPs <i>(local tourist information office), </i>and prepositional-NPs <i>(board of directors). </i>In English, the first two constructs are the most frequent.</p><p>OntoLearn uses a novel method for filtering "true" terminology, described in detail in (Velardi, Missikoff, and Basili 2001). The method is based on two measures, called <b>Domain Relevance </b>(DR) and <b>Domain Consensus </b>(DC), that we introduce hereafter.</p><table class="main" frame="box" rules="all" border="1" regular="False"><tr class="row"><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p>semantic interpretation</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p>semantic</p></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p>disambiguation</p></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p>V</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p>identification of</p></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p>taxonomic relations</p></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p>identification of</p></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p>conceptual relations</p></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td></tr></table><page local="6" global="156"/><p>High frequency in a corpus is a property observable for terminological as well as nonterminological expressions (e.g., <i>last week </i>or <i>real time). </i>We measure the specificity of a terminological candidate with respect to the target domain via comparative analysis across different domains. To this end a specific DR score has been defined. A quantita­tive definition of the DR can be given according to the amount of information captured within the target corpus with respect to a larger collection of corpora. More precisely, given a set of <i>n </i>domains {D1,<i>...</i>, <i>Dn} </i>and related corpora, the domain relevance of a term <i>t </i>in class <i>D</i><i>k</i><i> </i>is computed as where the conditional probabilities (P(t\Dk)) are estimated as where <i>ftik </i>is the frequency of term <i>t </i>in the domain <i>Dk </i>(i.e., in its related corpus).</p><doubt alpha="37.5" length="8" tooSmall="False" monospace="0.0">DRa= (1)</doubt><doubt alpha="42.9" length="7" tooSmall="False" monospace="0.0">P(t\D])</doubt><doubt alpha="20.0" length="5" tooSmall="False" monospace="0.0">1&lt;]&lt;n</doubt><doubt alpha="45.5" length="11" tooSmall="False" monospace="0.0">E(P(t\Dk))=</doubt><doubt alpha="57.1" length="7" tooSmall="False" monospace="0.0">Z^ff ,k</doubt><doubt alpha="80.0" length="5" tooSmall="False" monospace="0.0">t'eDk</doubt><p>Terms are concepts whose meaning is agreed upon by large user communities in a given domain. A more selective analysis should take into account not only the overall occurrence of a term in the target corpus but also its appearance in single documents. Domain terms (e.g., <i>travel agent) </i>are referred to frequently throughout the documents of a domain, while there are certain specific terms with a high frequency within single documents but completely absent in others (e.g., <i>petrol station, foreign income). </i>Dis­tributed usage expresses a form of <b>consensus </b>tied to the consolidated semantics of a term (within the target domain) as well as to its centrality in communicating domain knowledge.</p><p>A second relevance indicator, DC, is then assigned to candidate terms. DC mea­sures the distributed use of a term in a domain <i>Dk. </i>The distribution of a term <i>t </i>in documents <i>d £ Dk </i>can be taken as a stochastic variable estimated throughout all <i>d £ Dk. </i>The entropy of this distribution expresses the degree of consensus of <i>t </i>in Dk. More precisely, the domain consensus is expressed as follows:</p><doubt alpha="50.0" length="4" tooSmall="False" monospace="0.0">ft,]</doubt><doubt alpha="60.0" length="5" tooSmall="False" monospace="0.0">d]£Dk</doubt><p>Nonterminological (or nondomain) candidate terms are filtered using a combination of measures (1) and (2).</p><p>For each candidate term the following term weight is computed:</p><doubt alpha="60.0" length="10" tooSmall="False" monospace="0.0">\ftWlog -1</doubt><doubt alpha="100.0" length="4" tooSmall="False" monospace="0.0">deDk</doubt><doubt alpha="100.0" length="5" tooSmall="False" monospace="0.0">where</doubt><doubt alpha="100.0" length="4" tooSmall="False" monospace="0.0">norm</doubt><p><i>TW</i><i>t,k = </i><i>a</i><i>DR</i><i>tk + </i><i>P</i><i>D</i><b><i>Q</i></b> where <i>DC™™ </i>is a normalized entropy and <i>a,[3</i><i> </i><i>£</i><i> </i>(0,1). We experimented with several thresholds for <i>a</i><i> </i>and [, with consistent results in two domains (Velardi, Missikoff, and Basili 2001). Usually, a value close to 0.9 is to be chosen for a. The threshold for<page local="7" global="157"/></p><doubt alpha="71.4" length="7" tooSmall="False" monospace="0.0">Table 1</doubt><p>The first 10 terms from a tourism (left) and finance (right) domain.</p><doubt alpha="100.0" length="7" tooSmall="False" monospace="0.0">tourism</doubt><doubt alpha="100.0" length="7" tooSmall="False" monospace="0.0">finance</doubt><p>travel information vice president shopping street net income airline ticket executive officer booking form composite trading bus service stock market car rental interest rate airport transfer million share contact detail holding company continental breakfast third-quarter net tourist information offce    chief executive</p><doubt alpha="100.0" length="7" tooSmall="False" monospace="0.0">service</doubt><p>train service ferry service express service car ferry service public transport service</p><p><b>Figure 4</b></p><p>A lexicalized tree in a tourism domain.</p><p><i>[3</i><i> </i>depends upon the number <i>N </i>of documents in the training set of <i>Dk. </i>When <i>N </i>is sufficiently large, "good" values are between 0.35 and 0.25. Table 1 shows some of the accepted terms in two domains, ordered by <i>TW.</i></p></subsection><subsection number="3.2" title="Phase 2: Semantic Interpretation"><p>The set of terms accepted by the filtering method described in the previous section are first arranged in subtrees, according to simple string inclusion.<footnote anchor="5"/> Figure 4 is an example of what we call a <b>lexicalized </b>tree T. In absence of semantic interpretation, it is not possible to fully capture conceptual relationships between concepts (for example, the taxonomic relation between <i>bus service </i>and <i>public transport service </i>in Figure 4).</p><p>Semantic interpretation is the process of determining the right concept (sense) for each component of a <b>complex term </b>(this is known as <b>sense disambiguation) </b>and then identifying the semantic relations holding among the concept components, in order to build a <b>complex concept. </b>For example, given the complex term <i>bus service, </i>we would like to associate a complex concept with this term as in Figure 5, where bus#1 and <i>service#1 </i>are unique concept names taken from a preexisting concept inventory (e.g., WordNet, though other general-purpose ontologies could be used), and INSTR is a semantic relation indicating that there is a service, which is a type of work <i>(service</i>#1), operated through (instrument) a bus, which is a type of public transport <i>(bus</i>#1).</p><p>5 Inclusion is on the right side in the case of compound terms (the most common syntactic construct for terminology in English).</p><page local="8" global="158"/><doubt alpha="100.0" length="5" tooSmall="False" monospace="0.0">INSTR</doubt><p><b>Figure 5</b></p><p>A complex term represented as a complex concept.</p><p>This kind of semantic interpretation is indeed possible if the meaning of a new complex concept can be interpreted compositionally from its components. Clearly, this is not always possible. Furthermore, some of the component concepts may be absent in the initial ontology. In this case, other strategies can be adopted, as sketched in Section 6.</p><p>To perform semantic disambiguation, we use available lexical resources, like Word­Net and annotated corpora, and a novel word sense disambiguation (WSD) algorithm called <b>structural semantic interconnection. </b>A state-of-art inductive learner is used to learn rules for tagging concept pairs with the appropriate semantic relation.</p><p>In the following, we first describe the semantic disambiguation algorithm (Sec­tions 3.2.1 to 3.2.4). We then describe the semantic relation extractor (Section 3.2.5).</p><p><b>3.2.1 The Structural Semantic Interconnection Algorithm. </b>OntoLearn is a tool for extending and trimming a general-purpose ontology. In its current implementation, it uses a concept inventory taken from WordNet. WordNet associates one or more <b>synsets </b>(e.g., unique concept names) to over 120,000 words but includes very few domain terms: for example, <i>bus </i>and <i>service </i>are individually included, but not <i>bus service </i>as a unique term.</p><p>The primary strategy used by OntoLearn to attach a new concept under the ap­propriate hyperonym of an existing ontology is <b>compositional interpretation. </b>Let <i>t = wn • ... • </i>w2 <i>• </i>w1 be a valid multiword term belonging to a lexicalized tree <i>T</i>. Let <i>w</i>1 be the syntactic <b>head </b>of <i>t </i>(e.g., the rightmost word in a compound, or the leftmost in a prepositional NP). The process of compositional interpretation associates the appropriate WordNet synset <i>Sk </i>with each word <i>wk </i>in t. The <b>sense </b>of <i>t </i>is hence compositionally defined as where <i>Synsets(wk) </i>is the set of senses provided by WordNet for word wk, for instance:</p><p><i>S</i>("transport_company'') = [{transporfation#4, <i>shipping#l, transport#3 },</i> corresponding to sense 1 of <i>company </i>(an institution created to conduct business) and sense 3 of <i>transport </i>(the commercial enterprise of transporting goods and materials).</p><doubt alpha="66.7" length="12" tooSmall="False" monospace="0.0">{company#l}]</doubt><p>Compositional interpretation is a form of word sense disambiguation. In this sec­tion, we define a new approach to sense disambiguation called <b>structural semantic interconnections </b>(SSI).</p><p>The SSI algorithm is a kind of <b>structural pattern recognition. </b>Structural pattern recognition (Bunke and Sanfeliu 1990) has proven to be effective when the objects to be classified contain an inherent, identifiable organization, such as image data and time-series data. For these objects, a representation based on a "flat" vector of fea­tures causes a loss of information that has a negative impact on classification per(vehicle, passenger, transport) transport passenger <b>Figure 6</b><page local="9" global="159"/></p><doubt alpha="54.5" length="33" tooSmall="False" monospace="0.0">S(t) = [Sk\Sk£ Synsets(wk),wk£ t]</doubt><doubt alpha="33.3" length="3" tooSmall="False" monospace="0.0">(a)</doubt><doubt alpha="85.7" length="7" tooSmall="False" monospace="0.0">KIND-OF</doubt><doubt alpha="100.0" length="7" tooSmall="False" monospace="0.0">PURPOSE</doubt><doubt alpha="100.0" length="7" tooSmall="False" monospace="0.0">PATIENT</doubt><doubt alpha="100.0" length="7" tooSmall="False" monospace="0.0">vehicle</doubt><doubt alpha="100.0" length="5" tooSmall="False" monospace="0.0">coach</doubt><p>Two representations of the same concept: (a) as a feature vector and (b) as a semantic graph.</p><p>formances. The classification task in a structural pattern recognition system is imple­mented through the use of grammars that embody precise criteria to discriminate among different classes. The drawback of this approach is that grammars are by their very nature application and domain specific. However, automatic learning techniques may be adopted to learn from available examples.</p><p>Word senses clearly fall under the category of objects that are better described through a set of structured features. Compare for example the following two feature-vector (a) and graph-based (b) representations of the WordNet definition of <i>coach#5 </i>(a vehicle carrying many passengers, used for public transport) in Figure 6. The graph representation shows the semantic interrelationships among the words in the defini­tion, in contrast with the flat feature vector representation.</p><p>Provided that a graph representation for alternative word senses in a context is available, <i>disambiguation can be seen as the task of detecting certain "meaningful" intercon­necting patterns among such graphs. </i>We use a context-free grammar to specify the type of patterns that are the best indicators of a semantic interrelationship and to select the appropriate sense configurations accordingly.</p><p>In what follows, we first describe the method to obtain a graph representation of word senses from WordNet and other available resources. Then, we illustrate the disambiguation algorithm.</p><p><i>Creating a graph representation for word senses. </i>A graph representation of word senses is automatically built using a variety of knowledge source:</p><p>1.     WordNet. In WordNet, in addition to synsets, the following information is provided:</p><p>2. Domain labels<footnote anchor="6"/> extracted by a semiautomatic methodology described in Magnini and Cavaglia (2000) for assigning domain information (e.g., tourism, zoology, sport) to WordNet synsets.</p><p>3. Annotated corpora providing examples of word sense usages in contexts:</p><p>6 Domain labels have been kindly made available by the IRST to our institution for research purposes.</p><doubt alpha="28.6" length="7" tooSmall="False" monospace="0.0">(a) (b)</doubt><p>a textual sense definition (gloss); hyperonymy links (i.e., kind-of relations: for example, <i>bus#1 </i>is a kind of <i>puMicJmnsport#1);</i> meronymy relations (i.e., part-of relations: for example, bus#1 has part roo/#2 and <i>window#2);</i> other syntactic-semantic relations, as detailed later, not systematically provided throughout the lexical knowledge base.</p><doubt alpha="33.3" length="3" tooSmall="False" monospace="0.0">(c)</doubt><doubt alpha="33.3" length="3" tooSmall="False" monospace="0.0">(d)</doubt><page local="10" global="160"/><p>(a) SemCor<footnote anchor="7"/> is a corpus in which each word in a sentence is assigned a sense selected from the WordNet sense inventory for that word. Examples of a SemCor document are the following:</p><p><i>Color#l was delayed#l until 1935, the widescreen#l until the early#l fifties#l.</i></p><p><i>Movement#7 itself was#7 the chief#1 and often#l the only#l attraction#4 of the primitive#l movies#l ofthenineties#l.</i></p><p>(b) <i>LDC/DSO<footnote anchor="9"/> </i>is a corpus in which each document is a collection of sentences having a certain word in common. The corpus provides a sense tag for each occurrence of the word within the document. Examples from the document focused on the noun <i>house </i>are the following:</p><p><i>Ten years ago, he had come to the house#2 to be interviewed.</i></p><p><i>Halfway across the house#l, he could have smelled her morning perfume.</i></p><p>(c) In WordNet, besides glosses, examples are sometimes provided for certain synsets. From these examples, as for the LDC and SemCor corpora, co-occurrence information can be extracted. Some examples are the following:</p><p><i>Overnight accommodations#4 are available.</i></p><p><i>Is there intelligent#l life in the universe?</i></p><p><i>An intelligent#l question.</i></p><p>The use of other semantic knowledge repositories (e.g., FrameNet<footnote anchor="9"/> and Verbnet<footnote anchor="10"/>) is currently being explored, the main problem being the need of harmonizing these resources with the WordNet sense and relations inventory.</p><p>The information available in WordNet and in the other resources described in the previous section is used to automatically generate a labeled directed graph <b>(digraph) </b>representation of word senses. We call this a <b>semantic graph.</b></p><p>Figure 7 shows an example of the semantic graphs generated for senses 1 (coach) and 2 (conductor) of bus; in the figure, nodes represent concepts (WordNet synsets) and edges are semantic relations. In each graph in the figure, we include only nodes with a maximum distance of three from the central node, as suggested by the dashed oval. This distance has been experimentally established.</p><p>The following semantic relations are used: <b>hyperonymy </b><i>(car </i>is a kind of <i>vehicle,</i> denoted with kind—of), hyponymy (its inverse, hafL_kind), meronymy <i>(room </i>has-part <i>wall,</i></p><doubt alpha="64.3" length="28" tooSmall="False" monospace="0.0">has—part part—of • /7i• pert</doubt><p>—&gt; ), holonymy (its inverse, —&gt; ), pertamymy <i>(dental </i>pertams-to <i>tooth, </i>—<i>&gt;</i>), at­tribute (dry value-of <i>wetness, ___), </i>similarity <i>(beautiful </i>similar-to <i>pretty,</i>sim), gloss (gl_ss),</p></subsection></section><section number="7" title="http://www.cs.unt.edu/ ~rada/downloads.html#semcor"></section><section number="8" title="http://www.ldc.upenn.edu/"><p>9 http://www.icsi.berkeley.edu/~framenet/ 10 http://www.cis.upenn.edu/verbnet/<page local="11" global="161"/></p><doubt alpha="33.3" length="3" tooSmall="False" monospace="0.0">(a)</doubt><p>person#1 protection#2 transport#1 instrumentation#1 plate <b>j</b>glass#1 vehicle#1■lias-kind *q express#2 <b>i</b></p><doubt alpha="100.0" length="1" tooSmall="False" monospace="0.0">A</doubt><doubt alpha="51.9" length="27" tooSmall="False" monospace="0.0">^  #2roof#2Ö**.school bus#1</doubt><doubt alpha="59.2" length="49" tooSmall="False" monospace="0.0">"     ,. -Otraveler#A ^transport#1t^à-o^travele^1</doubt><doubt alpha="46.2" length="13" tooSmall="False" monospace="0.0">-    public ^</doubt><doubt alpha="66.7" length="6" tooSmall="False" monospace="0.0">pane#1</doubt><doubt alpha="50.0" length="2" tooSmall="False" monospace="0.0">A1</doubt><doubt alpha="44.4" length="9" tooSmall="False" monospace="0.0">'Sbss _ _</doubt><p>Ô/indow#<footnote anchor="2"/> framework#3' window frame#1 electricity#1 device#1</p><doubt alpha="0.0" length="2" tooSmall="False" monospace="0.0">05</doubt><p>»O-läiid-of</p><doubt alpha="55.0" length="20" tooSmall="False" monospace="0.0">% connection#1&lt;8&gt; &amp;v</doubt><p>^^js^'* ^Ainstrumentality#3</p><doubt alpha="71.4" length="7" tooSmall="False" monospace="0.0">union#4</doubt><p>electrical device#1 conductor#4 connection#2</p><doubt alpha="61.5" length="13" tooSmall="False" monospace="0.0">,-Y^nachine#1</doubt><p><b>Cj</b><b> </b>calculator#2 computer#1</p><p>wiring#1 <b>Figure 7</b></p><doubt alpha="33.3" length="3" tooSmall="False" monospace="0.0">(b)</doubt><p>Graph representations for (a) sense 1 and (b) sense 2 of bus.</p><p>topic (—&gt;), and domain (_). All these relations are explicitly encoded in WordNet, ex­cept for the last three. Topic, gloss, and domain are extracted from annotated corpora, sense definitions, and domain labels, respectively. Topic expresses a co-occurrence rela­tion between concepts in texts, extracted from annotated corpora and usage examples. Gloss relates a concept to another concept occurring in its natural language defini­tion. Finally, domain relates two concepts sharing the same domain label. In parsing glosses, we use a stop list to eliminate the most frequent words.</p><p><i>The SSI algorithm. </i>The SSI algorithm is a knowledge-based iterative approach to word sense disambiguation. The classification problem can be stated as follows:</p><doubt alpha="66.7" length="12" tooSmall="False" monospace="0.0">• tis a term</doubt><p><i>• T </i>(the <b>context </b>of t) is a list of co-occurring terms, including t.</p><p><i>• I </i>is a structural representation of <i>T </i>(the <b>semantic context).</b></p><doubt alpha="66.7" length="3" tooSmall="False" monospace="0.0">-Vv</doubt><doubt alpha="0.0" length="4" tooSmall="False" monospace="0.0">^ '\</doubt><page local="12" global="162"/><p><i>•</i><i> </i><i>St1, </i>S2, <i>■■■</i><i>, Stn </i>are structural specifications of the possible senses for <i>t </i><b>(semantic graphs).</b></p><p><i>•</i><i> </i><i>G </i>is a grammar describing structural relations <b>(semantic interconnections) </b>among the objects to be analyzed.</p><p><i>•</i><i> </i>Determine how well the structure of <i>I </i>matches that of each of</p><p><i>St1, St2,    </i>, <i>Stn, </i>using <i>G.</i></p><p><i>•</i><i> </i>Select the best matching.</p><p>Structural representations are graphs, as previously detailed. The SSI algorithm con­sists of an initialization step and an iterative step.</p><p>In a generic iteration of the algorithm, the input is a list of co-occurring terms <i>T </i>=[t1, <i>■ ■ ■ </i>, <i>tn] </i>and a list of associated senses <i>I </i><i>= </i><i>[St1,. </i><i>. . </i>, <i>Stn</i>], that is, the semantic interpretation of T, where <i>St{ </i><footnote anchor="11"/> is either the chosen sense for <i>t{ </i>(i.e., the result of a previous disambiguation step) or the empty set (i.e., the term is not yet disambiguated). A set of <i>pending </i>terms is also maintained, <i>P </i><i>= </i><i>{t{\St{ </i><i>= </i><i>0}. </i><i>I </i>is referred to as the semantic context of <i>T </i>and is used, at each step, to disambiguate new terms in P.</p><p>The algorithm works in an iterative way, so that at each stage either at least one term is removed from <i>P </i>(i.e., at least one pending term is disambiguated) or the procedure stops because no more terms can be disambiguated. The output is the updated list <i>I </i>of senses associated with the input terms <i>T.</i></p><p>Initially, the list <i>I </i>includes the senses of monosemous terms in <i>T. </i>If no monosemous terms are found, the algorithm uses an initialization policy described later.</p><p>During a generic iteration, the algorithm selects those terms <i>t </i>in <i>P </i>showing an interconnection between at least one sense <i>S </i>of <i>t </i>and one or more senses in <i>I. </i>The likelihood that a sense <i>S </i>will be the correct interpretation of <i>t, </i>given the semantic context I, is estimated by the function <i>fI</i>: <i>Synsets </i><i>x</i><i> </i><i>T </i><i>—</i><i> </i><i>3,</i><i> </i>where Synsets is the set of all the concepts in WordNet, and defined as follows:</p><doubt alpha="62.3" length="61" tooSmall="False" monospace="0.0">f(St) =/p({^(S,S')\S'eI})ifSeSenses(t)cSynsetsf(\ 0 otherwise</doubt><p>where <i>Senses(t) </i>is the subset of synsets in WordNet associated with the term <i>t, </i>and by semantic graphs. A semantic path between two senses <i>S</i><i> </i>and S', <i>S</i><i> </i><i>S1</i><i> </i><i>...</i><i> </i><i>e</i><i>-—</i><i><footnote anchor="1"/></i><i>Sn-1 S'</i>, is represented by a sequence of edge labels e1,e2,en. A proper choice for both <i>p</i><i> </i>and <i>p'</i><i> </i>may be the <b>sum </b>function (or the <b>average sum </b>function).</p><doubt alpha="64.4" length="146" tooSmall="False" monospace="0.0">4&gt;(S,S')= p'({w(eXle2, en)\S—S\—...—Sn-1-S'}),that is, a function (p')of the weights(w)of each path connectingSwith S', whereSandS'are represented</doubt><p>A context-free grammar <i>G</i><i> </i>= (E, <i>N,</i><i> </i><i>SG,</i><i> </i><i>PG)</i><i> </i>encodes all the meaningful semantic patterns. The terminal symbols (E) are edge labels, while the nonterminal symbols (N) encode (sub)paths between concepts; <i>SG </i>is the start symbol of G, and <i>PG </i>the set of its productions.</p><p>We associate a weight with each production <i>A </i><i>— </i><i>a </i><i>e </i><i>PG, </i>where <i>A </i><i>e </i><i>N </i>and <i>a </i><i>e </i><i>(N</i><i> </i><b>U </b>E)*, that is, <i>a </i>is a sequence of terminal and nonterminal symbols. If the sequence of edge labels e1,e2,<i>en </i>belongs to L(G), the language generated by the grammar, and <i>G</i><i> </i>is not ambiguous, then <i>w(e</i>1<i>,e</i>2,    <i>,e</i><i>n)</i><i> </i>is given by the sum of the</p><p>11 Note that with <i>St{ </i>we refer interchangeably to the semantic graph associated with a sense or to the <b>sense label </b>(i.e., the synset).</p><page local="13" global="163"/><p>weights of the productions applied in the derivation <i>SG </i><i>^</i><i>* </i>e1, e2,<i>...</i>, en. (The grammar <i>G </i>is described in the next subsection.)</p><p>Finally, the algorithm selects <i>St</i><i> </i>=argmax <i>fI(S,</i><i> </i><i>t)</i><i> </i>as the most likely interpretation of</p><p><i>S</i><i>e</i><i>Synsets</i></p><p><i>t</i><i> </i>and updates the list <i>I</i><i> </i>with the chosen concept. A threshold can be applied to <i>fI(S,</i><i> </i><i>t)</i><i> </i>to improve the robustness of the system's choices.</p><p>At the end of a generic iteration, a number of terms are disambiguated, and each of them is removed from the set of pending terms <i>P. </i>The algorithm stops with output <i>I </i>when no sense <i>S' </i>can be found for the remaining terms in <i>P </i>such that <i>fI</i><i>(S',</i><i> </i><i>t')</i><i> </i><i>&gt;</i><i> </i>0, that is, <i>P </i>cannot be further reduced. In each iteration, interconnections can be found only between the sense of a pending term <i>t </i>and the senses disambiguated during the previous iteration.</p><p>If no monosemous words are found, we explore two alternatives: either we provide manually the synset of the root term <i>h </i>(e.g., <i>service#1 </i>in Figure 4: work done by one person or group that benefits another), or we fork the execution of the algorithm into as many processes as the number of senses of the root term <i>h. </i>Let <i>n </i>be such a number. For each process <i>i</i><i> </i><i>(i</i><i> </i><i>= </i>1,..., n), the input is given by <i>I{ </i><i>= </i><i>[0,0,</i><i>...,</i><i> </i><i>Sh,...,</i><i> </i><b>0],</b><b> </b>where <i>Sh</i><i> </i>is the ith sense of <i>h </i>in <i>Senses </i><i>(h).</i><i> </i>Each execution outputs a (partial or complete) semantic context I{. Finally, the most likely context <i>Im </i>is obtained by choosing <b>3.</b><b>2.2 The Grammar. </b>The grammar <i>G </i>has the purpose of describing meaningful inter­connecting patterns among semantic graphs representing concepts in the ontology. We define a <b>pattern </b>as a sequence of consecutive semantic relations <i>e1-e2-...-en </i>where <i>e{ </i><i>e </i><i>E, </i>the set of terminal symbols, that is, the vocabulary of conceptual relations. Two rela­tions <i>e{ </i><i>• </i>e{+1 are consecutive if the edges labeled with <i>e{ </i>and e{+1 are incoming and/or outgoing from the same concept node, for example, <i>S <footnote anchor="1"/></i>, <i>S </i><i>£</i><i>- S <footnote anchor="1"/></i>, <i>S </i><i>ei+^.</i><i></i><i> </i>A <b>meaningful pattern </b>between two senses <i>S </i>and <i>S' </i>is a sequence <i>e</i>1 <i>•</i><i> </i><i>e</i>2 <i>•</i><i> </i><i>...</i><i> </i><i>•</i><i> </i><i>e</i><i>n </i>that belongs to <i>L(G).</i></p><doubt alpha="63.2" length="19" tooSmall="False" monospace="0.0">m=arg ma^^fIt(St,t)</doubt><footnote label="1">&lt; { &lt; n S t e h</footnote><figure caption="Figure 8 provides pseudocode for the SSI algorithm."></figure><p>In its current version, the grammar <i>G </i>has been defined manually, inspecting the intersecting patterns automatically extracted from pairs of manually disambiguated word senses co-occurring in different domains. Some of the rules in <i>G </i>are inspired by previous work in the eXtended WordNet<footnote anchor="12"/> project. The terminal symbols <i>e{ </i>are the conceptual relations extracted from WordNet and other on-line lexical-semantic resources, as described in Section 3.2.1.</p><p><i>G </i>is defined as a quadruple (E,N, Sg, Pg), where <i>E </i><i>= </i><i>{</i><i> </i>eWnd-of, ehas-kind, epart-of, ehas-part, egloss, eis-in-gloss, etopic, <i>■</i><i> </i><i>■■</i><i>}</i><i>,</i><i> </i><i>N</i><i> </i><i>= </i><i>{</i><i> </i><i>Sg</i>, Ss, Sg, S1, S2, S3, S4, S5, S6, E1, E2, <i>...</i><i>}</i><i>,</i><i> </i>and <i>PG </i>includes about 50 productions. An excerpt from the grammar is shown in Table 2.</p><p>As stated in the previous section, the weight w(e1,e2,<i>en)</i><i> </i>of a semantic path <i>e</i>1, <i>e</i>2, <i>,e</i><i>n </i>is given by the sum of the weights of the productions applied in the derivation <i>SG </i><i>^</i><i>* </i>e1, e2,<i>...</i>, en. These weights have been experimentally established on standard word sense disambiguation data, such as the SemCor corpus, and have been normalized so that the weight of a semantic path always ranges between 0 and 1.</p><p>The main rules in <i>G</i><i> </i>are as follows <i>(S1</i><i> </i>and <i>S2</i><i> </i>are two synsets in <i>I):</i></p><p>12 http://xwn.hlt.utdallas.edu/papers.html.</p><doubt alpha="33.3" length="3" tooSmall="False" monospace="0.0">16S</doubt><page local="14" global="164"/><p><i>SSI(T</i><i> </i>: list of terms, <i>I</i><i> </i>: initial list of interpretation synsets) for each <i>t </i><i>e</i><i> </i><i>T</i> if (t is monosemous) <i>I[t]</i><i> </i>= the only sense of <i>t</i></p><doubt alpha="0.0" length="1" tooSmall="False" monospace="0.0">{</doubt><doubt alpha="40.0" length="15" tooSmall="False" monospace="0.0">P:={teT:I[t]=0}</doubt><p><i>{ </i>while there are more terms to disambiguate <i>} </i>do</p><doubt alpha="40.0" length="5" tooSmall="False" monospace="0.0">P':=P</doubt><p>for each <i>t</i><i> </i><i>e </i><i>P'</i><i> </i><i>{ </i>for each pending term <i>}</i></p><doubt alpha="65.4" length="26" tooSmall="False" monospace="0.0">bestSense :=0maxValue := 0</doubt><p><i>{ </i>for each possible interpretation of <i>t </i><i>} </i>for each sense <i>S </i>of <i>t </i>in WordNet</p><doubt alpha="25.0" length="8" tooSmall="False" monospace="0.0">f[S]:= 0</doubt><p>for each synset <i>S' </i><i>e </i><i>I</i> if <i>(f[S]</i><i> </i><i>&gt;</i><i> </i>maxValue) maxValue := <i>f[S]</i><i> </i>bestSense := <i>S</i> <b>Figure 8</b></p><doubt alpha="14.3" length="7" tooSmall="False" monospace="0.0">&lt;i&gt;:= 0</doubt><doubt alpha="64.1" length="64" tooSmall="False" monospace="0.0">for each semantic pathe1e2...enbetweenSandS'4&gt;:=(f&gt;+w(e1e2...en)</doubt><doubt alpha="30.8" length="13" tooSmall="False" monospace="0.0">f[S]:=f[S]+4&gt;</doubt><doubt alpha="0.0" length="1" tooSmall="False" monospace="0.0">}</doubt><doubt alpha="66.7" length="15" tooSmall="False" monospace="0.0">if (maxValue&gt;0)</doubt><doubt alpha="58.3" length="24" tooSmall="False" monospace="0.0">I[t]:= bestSenseP:=P\{t}</doubt><doubt alpha="58.3" length="12" tooSmall="False" monospace="0.0">}while(P=P')</doubt><doubt alpha="100.0" length="7" tooSmall="False" monospace="0.0">returnI</doubt><p>The SSI algorithm in pseudocode.</p><page local="15" global="165"/><doubt alpha="71.4" length="7" tooSmall="False" monospace="0.0">Table 2</doubt><p>Excerpt from the context-free grammar for the recognition of semantic interconnections.</p><p><i>Sg </i><i>— </i><i>S</i><i>s</i><i>\S</i><i>g</i></p><doubt alpha="45.5" length="11" tooSmall="False" monospace="0.0">Ss—S1\S2\S3</doubt><footnote label="5">1 —  E 1 S 1 \  E 1</footnote><doubt alpha="60.0" length="25" tooSmall="False" monospace="0.0">E1     *ekind—of\epart—of</doubt><footnote label="5">2 —  E 2 S 2 \  E 2</footnote><p><i>E2     </i>* ehas—kind \ehas—part</p><footnote label="5">3 * e kind—of S 3 e has—kind \e kind—of e has—kind S g — e gloss S s \S 4 \S 5 \S 6</footnote><footnote label="5">4 * e gloss</footnote><footnote label="5">5 * e topic</footnote><footnote label="5">6 * e gloss e is—in—gloss</footnote><p>(all the rules) (simple rules) (hyperonymy/meronymy) (hyponymy/holonymy) (parallelism) (gloss rules) (gloss rule) (topic rule)</p><doubt alpha="66.7" length="21" tooSmall="False" monospace="0.0">(gloss + gloss—1rule)</doubt><p>1. color, if S1 is in the same adjectival cluster as <i>chromatic#3 </i>and S2 is a hyponym of a concept that can assume a color like <i>physical jobject#1 </i>and <i>food#1 </i>(e.g., S1 <i>= yellow#1 </i>and S2 <i>= wall#1)</i></p><p>2. domain, if the gloss of <i>S</i>1 contains one or more domain labels and <i>S</i>2 is a hyponym of those labels (for example, <i>white#3 </i>is defined as "(of wine) almost colorless," therefore it is the best candidate for <i>wine#1 </i>in order to disambiguate the term <i>wh{te w{ne)</i></p></section><section number="3." title="synonymy, if"><doubt alpha="45.0" length="40" tooSmall="False" monospace="0.0">(a) S1= S2or (b)3N e Synsets: S1—-N = S2</doubt><p>(for example, in the term <i>open a{r, </i>both the words belong to synset <i>{ open#8, air#2,outdoors#1 </i><i>})</i></p></section><section number="4." title="hyperonymy/meronymy path, if there is a sequence of"><p>has-part</p><p>hyperonymy/meronymy relations (for example, <i>mountain#1 —&gt;</i> <i>mountain peak#1 </i>kind-°f top#3 provides the right sense for each word of <i>mounta{n </i><i>top)</i></p></section><section number="5." title="hyponymy/holonymy path, if there is a sequence of"><p>hyponymy/holonymy relations (for example, in <i>sand beach, sand#1 p—-fbeach#1);</i></p><p>6. parallelism, if <i>S</i>1 and <i>S</i>2 have a common ancestor (for example, in <i>enterprise company, organization#1 </i>is a common ancestor of both <i>enterpr{se</i>#2 and <i>company</i>#1)</p><p>7. gloss, if S1 gl-ss S2 (for example, in <i>web site, </i>the gloss of web#5 contains the word site;in <i>waiter service, </i>the gloss of <i>restaurant attendant#1, </i>hyperonym of <i>waiter#1, </i>contains the word <i>service)</i></p><p>8. topic, if S1 —c S2 (for example, in the term <i>archeological site, </i>in which both words are tagged with sense 1 in a SemCor file; notice that WordNet provides no mutual information about them; also consider <i>picturesque village: </i>WordNet provides the example "a picturesque village" for sense 1 of <i>picturesque)</i><page local="16" global="166"/></p><p>9.     gloss+hyperonymy/meronymy path, if <i>3</i><i>G </i><i>e </i><i>Synsets </i>: S1 gl<b>-</b>ss <i>G </i>and there is a hyperonymy/meronymy path between <i>G </i>and <i>S</i>2 (for example, in <i>railway company, </i>the gloss of <i>railway</i><i>#1</i><i> </i>contains the word <i>organization </i>and <i>company</i><i>#1</i><i> </i><b>k--</b>°f <i>institution</i><i>#1</i><i> </i><i>k---oforganization</i><i>#1)</i></p><p>10. gloss+parallelism, if <i>3</i><i>G </i><i>e</i><i> </i><i>Synsets </i>: S1 gl<b>-</b>ss <i>G </i>and there is a parallelism path between <i>G </i>and <i>S</i>2 (for example, in <i>transport company, </i>the gloss of <i>transport</i>#3 contains the word <i>enterprise </i>and <i>organization</i>#1 is a common ancestor of both <i>enterprise</i>#2 and <i>company</i>#1)</p><p>11. gloss+gloss, if <i>3</i><i>G </i><i>e</i><i> </i><i>Synsets </i>: S1 gl<b>-</b>ss <i>G </i>gloss S2 (for example, in <i>mountain range, mountain</i>#1 and <i>range</i>#5 both contain the word <i>hill </i>so that the right senses can be chosen)</p><p>12. hyperonymy/meronymy+gloss path, if <i>3</i><i>G </i><i>e</i><i> </i><i>Synsets </i>: <i>G      S2 </i>and there is a hyperonymy/meronymy path between <i>S</i>1 and <i>G</i></p><p>13. parallelism+gloss, if <i>3</i><i>G </i><i>e</i><i> </i><i>Synsets </i>: <i>G </i>gloss S2 and there is a parallelism path between <i>S</i>1 and <i>G.</i></p><p><b>3.2.3 A Complete Example. </b>We now provide a complete example of the SSI algorithm applied to the task of disambiguating a lexicalized tree <i>T</i>. With reference to Figure 4, the list <i>T </i>is initialized with all the component words in <b>T, </b>that is, [service, train, ferry, car, boat, car-ferry, bus, coach, transport, public-transport, taxi, express, customer].</p><p>Step 1. In <i>T </i>there are four monosemous words, <i>taxi, car-ferry, public-transport, </i>and <i>customer; </i>therefore, we have <i>P = </i>{service, train, ferry, car, boat, bus, coach, transport, express}.</p><doubt alpha="65.5" length="55" tooSmall="False" monospace="0.0">I=[taxi#1, car_ferry#1, public_transport#1, customer#1]</doubt><p>Step 2. During the second iteration, the following rules are matched:<footnote anchor="13"/> <i>{taxi} </i>kind-°f <b>{</b>car, auto}(hyper) {taxi} kind-°f <b>{</b>car, auto} kind-°f <b>{</b>motor_vehicle,automotive_vehicle} <i>k</i><i>m</i><i>-of</i><i> </i><b>{</b>vehicle} gloss <b>{</b>bus,autobus,coach}(hyper <i>+ </i>gloss) {taxi} <i>kim--of</i><i> </i><b>{</b>car, auto} <b>kim-</b>°f <b>{</b>motor_vehicle,automotive_vehicle} <b>'"i--^ {</b>vehicle} gloss <b>{</b>ferry, ferryboat} (hyper <i>+ </i>gloss)</p><doubt alpha="65.3" length="98" tooSmall="False" monospace="0.0">{bus, autobus, coach}'"i--^ {public_transport} (hyper) {carferry}'"i--^ {ferry, ferryboat} (hyper)</doubt><p>13 More than one rule may contribute to the disambiguation of a term. We list here only some of the detected patterns.</p><page local="17" global="167"/><doubt alpha="65.0" length="40" tooSmall="False" monospace="0.0">{customer, client}      {service}(topic)</doubt><doubt alpha="39.4" length="33" tooSmall="False" monospace="0.0">,        .    , gloss has-kindr-,</doubt><p>{service} —<b><i>&gt; </i></b><b>{</b>person, someone} —&gt;  <b>{</b>consumer} has_kind <b>{</b>customer, client}(gloss + hypo) {train, railroad-train} kl-d^! <b>{</b>public_transport} (hyper) {express, expressbus} k<b>—</b>r<b>L? </b>{bus, autobus, coach} kl<b>—1° {</b>public-transport}(hyper) {conveyance, transport} has_kind <b>{</b>public-transport}(hypo) obtaining:</p><doubt alpha="59.7" length="134" tooSmall="False" monospace="0.0">I =[taxi#1, car_ferry#1, public_transport#1, customer#1, car#1, ferry#1, bus#1, coach#5, train#1, express#2, transport#1, service#1]14</doubt><p><i>P = {boat}.</i></p><p>Step 3.</p><p>{boat} ha<b>-</b>s_kind <b>{</b>ferry, ferryboat}(hypo)</p><doubt alpha="59.3" length="140" tooSmall="False" monospace="0.0">I =[taxi#1, car_ferry#1, publi^transport#1, customer#1, car#1, ferry#1, bus#1, coach#5, train#1, express#2, boat#1, transport#1, service#1 ]</doubt><p>P = <i>9.</i></p><p>Then the algorithm stops since the list <i>P </i>is empty.</p><p><b>3.2.4 Creating Domain Trees. </b>During the execution of the SSI algorithm, (possibly) all the terms in a lexicalized tree <i>T</i><i> </i>are disambiguated. Subsequently, we proceed as follows:</p><p>a. Concept clustering: Certain concepts can be clustered in a unique concept on the basis of pertainymy, similarity, and synonymy (e.g., <i>manor house </i>and <i>manorial house, expert guide </i>and <i>skilled guide, bus service </i>and <i>coach service, </i>respectively); notice again that we detect semantic relations between concepts, not words. For example, bus#1 and <i>coach#5 </i>are synonyms, but this relation does not hold for other senses of these two words.</p><p>b. Hierarchical structuring: Taxonomic information in WordNet is used to replace syntactic relations with kind-of relations (e.g., <i>ferry service </i><b>'"ikL^ </b><i>boat service), </i>on the basis of hyperonymy, rather than string inclusion as n .</p><p>14 Not ce that <i>bus</i>#1 and <i>coach</i>#5 belong to the same synset, therefore they are d samb guated by the same rule.</p><page local="18" global="168"/><p><b>Figure 9</b></p><p>Domain concept tree.</p><p>Each lexicalized tree <i>T </i>is finally transformed into a <b>domain concept tree </b>T. Fig­ure 9 shows the concept tree obtained from the lexicalized tree of Figure 4. For the sake of legibility, in Figure 9 concepts are labeled with the associated terms (rather than with synsets), and numbers are shown only when more than one semantic in­terpretation holds for a term. In fact, it is possible to find more than one matching hyperonymy relation. For example, an <i>express </i>can be a <i>bus </i>or a <i>train, </i>and both inter­pretations are valid, because they are obtained from relations between terms within the domain.</p><p><b>3.2.5 Adding Conceptual Relations. </b>The second phase of semantic interpretation in­volves finding the appropriate semantic relations holding among concept components. In order to extract semantic relations, we need to do the following:</p><p><i>• </i>Select an inventory of domain-appropriate semantic relations.</p><p><i>• </i>Learn a formal model to select the relations that hold between pairs of concepts, given ontological information on these concepts.</p><p><i>• </i>Apply the model to semantically relate the components of a complex concept.</p><p>First, we selected an inventory of semantic relations types. To this end, we con­sulted John Sowa's (1984) formalization on conceptual relations, as well as other studies conducted within the CoreLex,<footnote anchor="15"/> FrameNet, and EuroWordNet (Vossen 1998) projects. In the literature, no systematic definitions are provided for semantic relations; therefore we selected only the more intuitive and widely used ones.</p><p>To begin, we selected a kernel inventory including the following 10 relations, which we found pertinent (at least) to the tourism and finance<footnote anchor="16"/> domains: place (e.g., <i>room &lt;— service, </i>which reads "the service <u>has</u> place in a room" or "the room is the place of service"), time <i>(afternoon </i><i>T^M-</i><i> tea), </i>matter <i>(ceramics </i>M^T-ER tiZe), topic (art</p><doubt alpha="100.0" length="5" tooSmall="False" monospace="0.0">PLACE</doubt><p>TOPIC     „     . MANNER .        , BENEF . .</p><p><i>&lt;— gaZZery), </i>manner (bus <i>&lt;</i>— <i>service), </i>beneficiary <i>(customer &lt;— service), </i>purpose <i>(booking </i>PURpOSE <i>service), </i>object <i>(wine </i><i>+<footnote anchor="0"/>-</i><i> production), </i>attribute <i>(historicaZ </i>AT-R <i>town),</i></p></section><section number="15" title="http://www.cs.brandeis.edu/~paulb/CoreLex/corelex.html"><p>16 Financial terms are extracted from the <i>Wall Street Journal.</i></p><page local="19" global="169"/><p>characteristics <i>(first-class </i>CH<i>—</i>-C <i>hotel). </i>This set can be easily adapted or extended to other domains.</p><p>In order to associate the appropriate relation(s) that hold among the components of a domain concept, we decided to use <b>inductive machine learning. </b>In inductive learning, one has first to manually tag with the appropriate semantic relations a subset of domain concepts (this is called the <b>learning set) </b>and then let an inductive learner build a tagging model. Among the many available inductive learning programs, we experimented both with Quinlan's C4.5 and with TiMBL (Daelemans et al. 1999).</p><p>An inductive learning system requires selecting a set of features to represent in­stances in the learning domain. Instances in our case are concept-relation-concept triples (e.g., <i>wine &lt;</i>°O<i>— production), </i>where the type of relation is given only in the learning set.</p><p>We explored several alternatives for feature selection. We obtained the best result when representing each concept component by the complete list of its hyperonyms (up to the topmost), as follows:</p><p>feature - vector[[list_of_hyperonyms]modifier [list-of_hyperonyms]head]</p><p>For example, the feature vector for <i>tourism operator, </i>where <i>tourism </i>is the modifier and <i>operator </i>is the head, is built as the sequence of hyperonyms of <i>tourism#1: </i>[tourism#1, commerciaLenterprise#2, commerce#1, transaction#1, group-action#1, act#1, human-action#1], followed by the sequence of hyperonyms for <i>operator#2 </i>[operator#2, capi-talist#2, causal_agent#1, entity#1, life_form#1, person#1, individual#1].</p><p>Features are converted into a binary representation to obtain vectors of equal length. We ran several experiments, using a tagged set of 405 complex concepts, a varying fragment of which were used for learning, the remainder for testing (we used two-fold cross-validation). Overall, the best experiment provided a 6% error rate over 405 examples and produced around 20 classification rules.</p><p>The following are examples of extracted rules (from C4.5), along with their confi­dence factor (in parentheses) and examples:</p><p><u>If in modifier</u> [knowledge_domain#1, knowledge_base#1 ] = 1 <u>then relation</u> THEME(63%) Examples : arts_festival, science_center <u>If in modifier</u> [building_material#1 ] = 1 <u>then relation</u> MATTER(50%) Examples : stave_church, cobblestone_street</p><doubt alpha="66.2" length="77" tooSmall="False" monospace="0.0">If in modifier[conveyance#3, transport#1 ] = 1and in head[act#1,human_act#1 ]</doubt><doubt alpha="62.1" length="29" tooSmall="False" monospace="0.0">= 1then relationMANNER(92.2%)</doubt><p>Examples : bus_service, coach.tour</p><p>Selection and extraction of conceptual relations is one of the active research areas in the OntoLearn project. Current research is directed toward the exploitation of on-line resources (e.g., the tagged set of conceptual relations in FrameNet) and the automatic generation of glosses for complex concepts (e.g., for <i>travel service </i>we have <i>travel</i>#1<page local="20" global="170"/></p><doubt alpha="100.0" length="7" tooSmall="False" monospace="0.0">PURPOSE</doubt><p><i>&lt;</i><i>— service#1</i><b><i>:"a </i></b><b>kind </b>of service, work done by one person or group that benefits another, <b>for </b>travel, the act of going from one place to another"). Automatic generation of glosses (see Navigli et al. [2004] for preliminary results) relies on the compositional interpretation criterion, as well as the semantic information provided by conceptual relations.</p><subsection number="3.3" title="Phase 3: Ontology Integration"><p>The domain concept forest generated by OntoLearn is used to trim and update Word­Net, creating a domain ontology. WordNet is pruned and trimmed as follows:</p><p><i>•</i><i> </i>After the domain concept trees are attached to the appropriate nodes in WordNet in either a manual or an automatic manner, all branches not containing a domain node can be removed from the WordNet hierarchy.</p><p><i>•</i><i> </i>An intermediate node in WordNet is pruned whenever the following conditions all hold:</p><p>1. It has no "brother" nodes.</p><p>2. It has only one direct hyponym.</p><p>3. It is not the root of a domain concept tree.</p><p>4. It is not at a distance greater than two from a WordNet unique beginner (this is to preserve a "minimal" top ontology).</p><p>Figure 10 shows an example of pruning the nodes located over the domain concept tree rooted at <i>wine</i>#1. The appendix shows an example of a domain-adapted branch of WordNet in the tourism domain.</p></subsection></section><section number="4." title="Evaluation"><p>The evaluation of ontologies is recognized to be an open problem.<footnote anchor="17"/> Though the num­ber of contributions in the area of ontology learning and construction has considerably increased in the past few years, especially in relation to the forthcoming Semantic Web, experimental data on the utility of ontologies are not available, other than those in Far-quhar et al. (1998), in which an analysis of user distribution and requests is presented for the Ontology Server system. A better performance indicator would have been the number of users that access the Ontology Server on a regular basis, but the authors mention that regular users account for only a small percentage of the total. Efforts have recently being made on the side of ontology evaluation tools and methods, but available results are on the methodological rather than on the experimental side. The ontology community is still in the process of assessing an evaluation framework.</p><p>We believe that, in absence of a commonly agreed-upon schema for analyzing the properties of an ontology, the best way to proceed is evaluating an ontology <i>within </i>some existing application. Our current work is precisely in this direction: The results of a terminology translation experiment appear in Navigli, Velardi, and Gangemi (2003), while preliminary results on a query expansion task are presented in Navigli and</p><p>Velardi (2003).</p><p>17 OntoWeb D.1.S Tools (2001), "Whitepaper: Ontology Evaluation Tools," available at http://www.aifb.unikarlsruhe.de/WBS/ysu/publications/eon200^whitepaper.pdf<page local="21" global="171"/></p><doubt alpha="66.7" length="9" tooSmall="False" monospace="0.0">Figure 10</doubt><p>Pruning steps over the domain concept tree for <i>wine</i><i>1.</i></p><p>In this evaluation section we proceed as follows: First, we provide an account of the feedback that we obtained from tourism experts participating in the Harmonise EC project on interoperability in the tourism domain. Then, we evaluate in detail the SSI algorithm, which is the "heart" of the OntoLearn methodology.</p><subsection number="4.1" title="OntoLearn as a Support for Ontology Engineers"><p>During the first year of the Harmonise project, a core ontology of about three hundred concepts was developed using ConSys and SymOntoX. In parallel, we collected a corpus of about one million words from tourism documents, mainly descriptions of travels and tourism sites. From this corpus, OntoLearn extracted an initial list of 14,383 candidate terms (the first phase of terminology extraction in Section 3.<page local="22" global="172"/>1), from which the system derived a domain concept forest of 3,840 concepts, which were submitted to the domain experts for ontology updating and integration.</p><p>The Harmonise ontology partners lacked the requisite expertise to evaluate the WordNet synset associations generated by OntoLearn for each complex term, therefore we asked them to evaluate only the domain appropriateness of the <i>terms, </i>arranged in a hierarchical fashion (as in Figure 9). We obtained a precision ranging from 72.9% to about 80% and a recall of 52.74%.<footnote anchor="18"/> The precision shift is due to the well-known fact that experts may have different intuitions about the relevance of a concept for a given domain. The recall estimate was produced by manually inspecting 6,000 of the initial 14,383 candidate terms, asking the experts to mark all the terms judged as "good" domain terms, and comparing the obtained list with the list of terms automatically filtered by OntoLearn (the phase of terminology filtering described in Section 3.1).</p><p>As a result of the feedback obtained from the tourism experts, we decided that experts' interpretation difficulties could indeed be alleviated by associating a textual definition with each new concept proposed by OntoLearn. This new research (auto­matic generation of glosses) was mentioned in Section 3.2.5. We still need to produce an in-field evaluation of the improved readability of the ontology enriched with textual definitions.</p><p>In any case, OntoLearn favored a considerable speed up in ontology development, since shortly after we provided the results of our OntoLearn tool, the Harmonise ontology reached about three thousand concepts. Clearly, the definition of an initial set of basic domain concepts is sufficiently crucial, to justify long-lasting and even heated discussions. But once an agreement is reached, filling the lower levels of the ontology can still take a long time, simply because it is a tedious and time-consuming task. Therefore we think that OntoLearn revealed itself indeed to be a useful tool within Harmonise.</p></subsection><subsection number="4.2" title="Evaluation of the SSI Word Sense Disambiguation Algorithm"><p>As we will argue in Section 5, one of the novel aspects of OntoLearn with respect to current ontology-learning literature is semantic interpretation of extracted terms. The SSI algorithm described in section 3.2 was subjected to several evaluation exper­iments by the authors of this article. The output of these experiments was used to tune certain heuristics adopted by the algorithm, for example, the dimension of the semantic graph (i.e., the maximum distance of a concept <i>S' </i>from the central concept S) and the weights associated with grammar rules. To obtain a domain-independent tuning, tuning experiments were performed applying the SSI algorithm on standard word sense disambiguation data,<footnote anchor="19"/> such as SemCor and Senseval all-words.<footnote anchor="20"/></p><p>However, OntoLearn's main task is terminology disambiguation, rather than plain word sense disambiguation. In complex terms, words are likely to be more tightly se-mantically related than in a sentence; therefore the SSI algorithm seems more appropriate.<footnote anchor="21"/> To test the SSI algorithm, we selected 650 complex terms from the set of 3,840 concepts mentioned in Section 4.1, and we manually assigned the appropriate</p><p>18 In a paper specifically dedicated to terminology extraction and evaluation (Velardi, Missikoff, and Basili 2001) we performed an evaluation also on an economics domain, with similar results.</p><p>19 In standard WSD tasks, the list <i>T </i>in input to the SSI algorithm is the set of all words in a sentence fragment to be disambiguated.</p><p>20 http://www.itri.brighton.ac.uk/events/senseval/ARCHIVE/resources.html#test</p><p>21 For better performance on a standard WSD task, it would be essential to improve lexical knowledge of verbs (e.g. by integrating VerbNet and FrameNet, as previously mentioned), as well as to enhance the grammar.</p><page local="23" global="173"/><doubt alpha="0.0" length="38" tooSmall="False" monospace="0.0">90% 80% 70% 60% 50% 40% 30% 20% 10% 0%</doubt><p>□ including monosemous terms</p><p>□ excluding monosemous terms</p><doubt alpha="66.7" length="9" tooSmall="False" monospace="0.0">Figure 11</doubt><p>Different runs of the semantic disambiguation algorithm when certain rules in the grammar <i>G </i>are removed.</p><p>WordNet synset to each word composing the term. We used two annotators to ensure some degree of objectivity in the test set. In this task we experienced difficulties al­ready pointed out by other annotators, namely, that certain synsets are very similar, to the point that choosing one or the other—even with reference to our specific tourism domain—seemed a mere guess. Though we can't say that our 650 tagged terms are a "gold standard," evaluating OntoLearn against this test set still produced interest­ing outcomes and a good intuition of system performance. Furthermore, as shown by the example of Section 3.2.3, OntoLearn produces a motivation for its choices, that is, the detected semantic patterns. Though it was not feasible to analyze in detail all the output of the system, we found more than one example in which the choices of OntoLearn were more consistent<footnote anchor="22"/> and more convincing than those produced by the annotators, to the point that OntoLearn could also be used to support human annotators in disambiguation tasks.</p><p>First, we evaluated the effectiveness of the rules in <i>G </i>(Section 3.2.2) in regard to the disambiguation algorithm. Since certain rules are clearly related (for example, rules 4 and 5, rules 9 and 11), we computed the precision of the disambiguation when adding or removing groups of rules. The results are shown in Figure 11. The shaded bars in the figure show the results obtained when those terms containing unambiguous words are removed from the set of complex terms.</p><p>We found that the grammar rules involving the gloss and hyperonym relations contribute more than others to the precision of the algorithm. Certain rules (not listed in 3.2.2 since they were eventually removed) were found to produce a negative effect. All the rules described in 3.2.2 were found to give more or less a comparable positive contribution to the final performance.</p><p>22 Consistent at least with respect to the lexical knowledge encoded in WordNet.</p><doubt alpha="33.3" length="3" tooSmall="False" monospace="0.0">l73</doubt><table class="main" frame="box" rules="all" border="1" regular="False"><tr class="row"><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p><b>00</b></p></td><td class="cell"><p></p></td><td class="cell"><p><b>00</b></p></td><td class="cell"><p></p></td><td class="cell"><p><b>QQ</b></p></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td></tr></table><page local="24" global="174"/><doubt alpha="0.0" length="36" tooSmall="False" monospace="0.0">100% 90% 80% 70% 60% 50% 40% 30% 20%</doubt><doubt alpha="0.0" length="6" tooSmall="False" monospace="0.0">10% 0%</doubt><doubt alpha="65.2" length="46" tooSmall="False" monospace="0.0">manually dis. head □ precision        □ recall</doubt><p>fully automatic</p><doubt alpha="66.7" length="9" tooSmall="False" monospace="0.0">Figure 12</doubt><p>Precision and recall for the terminology disambiguation task: manual disambiguation of the head and fully automatic disambiguation.</p><p>The precision computed in Figure 11 refers to the case in which the head node of each term tree is sense-tagged manually. In Figure 12 the light and dark bars represent precision and recall, respectively, of the algorithm when the head (i.e., the root) of a term tree is manually assigned and when the disambiguation is fully automatic. The limited drop in performance (2%) of the fully automated task with respect to manual head disambiguation shows that, indeed, the assumption of a strong semantic interrelationship between the head and the other terms of the term tree is indeed justified.</p><p>Finally, we computed a baseline, comparing the performance of the algorithm with that obtained by a method that always chooses the first synset for each word in a com­plex term. (We remind readers that in WordNet, the first sense is the most probable.) The results are shown in Figure 13, where it is seen, as expected, that the increment in performance with respect to the baseline is higher (around 5%) when only polyse-mous terms are considered. A 5% difference (3% with respect to the fully automatic disambiguation) is not striking, however, the tourism domain is not very technical, and often the first sense is the correct one. We plan in the future to run experiments with more technical domains, for example, economics or software products.</p></subsection></section><section number="5." title="Related Work"><p>Comprehensive ontology construction and learning has been an active research field in the past few years. Several workshops<footnote anchor="23"/> have been dedicated to ontology learning and related issues. The majority of papers in this area propose methods for extending an existing ontology with unknown words (e.g., Agirre et al. 2000 and Alfonseca and Manandhar 2002). Alfonseca and Manandhar present an algorithm to enrich WordNet with unknown concepts on the basis of hyponymy patterns. For example, the pattern <i>hypernism(N2, </i><i>N1)</i><i> </i>: <i>-appositive(N2, </i><i>N1)</i><i> </i>captures a hyponymy relation between <i>Shake­speare </i>and <i>poet </i>in the appositive NP "Shakespeare, the poet." This approach heavily</p><p>23 ECAI-2000 First Workshop on Ontology Learning (http://ol2000.aifb.uni-karlsruhe.de/) and IJCAI-2001 Second Workshop on Ontology Learning (http://ol2001.aifb.uni-karlsruhe.de/).</p><table class="main" frame="box" rules="all" border="1" regular="False"><tr class="row"><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p>II      <b>3    1             </b>3 <b>g</b></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p><b>66 °°. ,</b><b>-</b><b>. m</b></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p><b>—r</b><b>--</b></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"><p></p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td><td class="cell"></td></tr></table><page local="25" global="175"/><p>□ including monosemous terms</p><p>□ excluding monosemous terms</p><doubt alpha="0.0" length="19" tooSmall="False" monospace="0.0">90% 80% 70% 60% 50%</doubt><doubt alpha="0.0" length="3" tooSmall="False" monospace="0.0">40%</doubt><doubt alpha="0.0" length="7" tooSmall="False" monospace="0.0">30% 20%</doubt><doubt alpha="0.0" length="3" tooSmall="False" monospace="0.0">10%</doubt><doubt alpha="0.0" length="2" tooSmall="False" monospace="0.0">0%</doubt><p>best result baseline</p><doubt alpha="66.7" length="9" tooSmall="False" monospace="0.0">Figure 13</doubt><p>Comparison with a baseline.</p><p>depends upon the ability of discovering such patterns, however, it appears a useful complementary strategy with respect to OntoLearn. OntoLearn, in fact, is unable to analyze totally unknown terms (though ongoing research is in progress to remedy this limitation). Berland and Charniak (1999) propose a method for extracting whole-part relations from corpora and enrich an ontology with this information. Few papers pro­pose methods of extensively enriching an ontology with domain terms. For example, Vossen (2001) uses statistical methods and string inclusion to create lexicalized trees, as we do (see Figure 4). However, no semantic disambiguation of terms is performed. Very often, in fact, ontology-learning papers regard domain <i>terms as concepts. </i>A statis­tical classifier for automatic identification of semantic roles between co-occuring terms is presented in Gildea and Jurafsky (2002). In order to tag texts with the appropriate semantic role, Gildea and Jurafsky use a training set of fifty thousand sentences man­ually annotated within the FrameNet semantic labeling project. Finally, in Maedche and Staab (2000, 2001), an architecture is presented to help ontology engineers in the difficult task of creating an ontology. The main contribution of this work is in the area of ontology engineering, although machine-learning methods are also proposed to automatically enrich the ontology with semantic relations.</p></section><section number="6." title="Conclusions and Ongoing Developments"><p>We believe that the OntoLearn system is innovative in several respects:</p><p>1. in presenting an overall ontology development system.</p><p>2. in stressing the importance of appropriate terminology extraction to the ontology-building enterprise.</p><p>3. in avoiding a common confusion between domain <i>terms </i>and domain <i>concepts, </i>since it performs a <i>semantic interpretation </i>of terms. This is indeed the strongest aspect of our method.</p><page local="26" global="176"/><p>4.     in presenting a new structural approach to sense classification (SSI). This method is general and has been applied to other sense disambiguation tasks, such as sense-based query expansion (Navigli and Velardi 2003) and gloss disambiguation (Gangemi, Navigli, and Velardi 2003).</p><p>Ontology learning is a complex enterprise, and much is left to be done. We list here some of the drawbacks and gaps of our method, along with hints for ongoing and future developments. OntoLearn is in fact a fully active area of research within our group.</p><p>1. The SSI method presupposes that each term component has at least one synset in WordNet. In our ongoing research, we try to cope with this limitation, parsing textual definitions in glossaries (e.g., in a computer network application) whenever a term cannot be interpreted compositionally in WordNet. Terms in glossaries are first arranged in trees according to detected taxonomic relations, then the head terms of each tree are attached to the appropriate node of WordNet, if an appropriate node indeed exists. Rule-based and algebraic methods are jointly used to construct term trees and to compute measures of the similarity between the textual definitions in glossaries and those in</p><p>WordNet.</p><p>2. OntoLearn detects taxonomic relations between complex concepts and other types of semantic relations among the components of a complex concept. However, an ontology is more than a taxonomy. The result of concept disambiguation in OntoLearn is more than an ordered list of synsets, since we obtain semantic nets and intersecting patterns among them (Section 3.2.2). This information is not currently exploited to generate richer concept definitions. A preliminary attempt to generate formal concept definitions from informal ones is described in Gangemi, Navigli, and Velardi (2003). Furthermore, an automatic gloss generation algorithm has been defined (Navigli et al. 2004).</p><p>3. A large-scale evaluation is still to be done. As we have already pointed out, evaluation of ontologies is recognized as an open problem, and few results are available, mostly on the procedural ("how to") side. We partly evaluated OntoLearn in an automatic translation task (Navigli, Velardi, and Gangemi 2003), and the SSI algorithm in generic WSD tasks as mentioned in item 4 of the previous list. In addition, it would be interesting to run OntoLearn on different domains, in order to study the effect of higher or lower levels of ambiguity and technicality on the output domain ontology.</p></section><references><p>Agirre, Eneko, Olatz Ansa, Eduard, Hovy, and David Martinez. 2000. Enriching very large ontologies using the WWW. In <i>ECAI Ontology Learning Workshop 2000, </i>available at http://ol2000.aifb.uni-karlsruhe.de/</p><p>Alfonseca, Enrique and Suresh Manandhar. 2002. Improving an ontology refinement Method with hyponymy patterns. In <i>Language Resources and Evaluation (LREC-2002), </i>LasPalmas, Spain, May.</p><p>Basili, Roberto, Maria Teresa Pazienza, and Paola Velardi. 1996. An empirical symbolic approach to natural language processing, <i>Artificial Intelligence, </i>85(1-2): 59-99.</p><p>Basili, Roberto, Maria Teresa Pazienza, and Fabio Massimo Zanzotto. 1998. A robust parser for information extraction. In <i>Proceedings of the European Conference on Artificial Intelligence (ECAI '98), </i>Brighton, U.K., August.</p><p>Berland, Matthew and Eugene Charniak. 1999. Finding parts in very large corpora. In <i>Proceedings of the the 37th Annual Meeting of the Association for Computational</i> <i>Linguistics (ACL-99), </i>College Park, MD.</p><p>Berners-Lee, Tim. 1999. <i>Weaving the Web.</i></p><p>Harper, San Francisco. Bunke, Horst and Alberto Sanfeliu, editors.</p><p>1990. <i>Syntactic and Structural Pattern</i> <i>Recognition:</i><i> Theory and Applications. </i>World</p><p>Scientific.</p><p>Church, Kenneth Ward and Patrick Hanks. 1989. Word association norms, mutual information and lexicography. In <i>ACL-89, </i>Vancouver, British Columbia, Canada.</p><p>Daelemans, Walter, Jakub Zavrel, Ko van der Sloot, and Antal van den Bosch. 1999. TiMBL: Tilburg Memory Based Learner, version 2.0, reference manual. Technical</p><p>Report ILK-9901, ILK, Tilburg University,</p><p>Tilburg, the Netherlands. Farquhar, Adam, Richard Fikes, Wanda</p><p>Pratt, and James Rice. 1998.</p><p>"Collaborative Ontology Construction for Information Integration." http://www-ksl-svc.stanford.edu:5915/doc/project-papers.html.</p><p>Fellbaum, Christiane, editor. 1995. <i>WordNet: An Electronic Lexical Database. </i>MIT Press, Cambridge, MA.</p><p>Formica, Anna, and Michele Missikoff. 2003.</p><p>Ontology Validation in OPAL. In <i>2003</i> <i>International Conference on Web Services (ICWS' 03), </i>Las Vegas, NV. Springer. Gangemi, Aldo, Nicola Guarino, Claudio Masolo, Alessandro Oltramari, and Luc Schneider. 2001. Sweetening ontologies with DOLCE. In <i>Proceedings ofEKAW02, </i>Siguenza, Spain. Springer, pages 166-181</p><p>Gangemi, Aldo, Roberto Navigli, and Paola Velardi. 2003. Axiomatising WordNet: A hybrid methodology. In <i>Workshop on Human Language Technology for the Semantic Web and Web Services, </i>Held in Conjunction with <i>Second International Semantic Web Conference, </i>Sanibel Island, FL.</p><p>Gildea, Daniel and Daniel Jurafsky. 2002. Automatic labeling of semantic roles. <i>Computational Linguistics, </i>28(3): 245-288.</p><p>Jacquemin, Christian. 1997. Guessing morphology from terms and corpora. In <i>Proceedings ofthe 20th Annual International ACM SIGIR Conference on Research and Development in Information Retrieval (SIGIR' 97), </i>Philadelphia, PA, pages 156-167.</p><p>Lenat, Douglas. 1993. CYC: A large scale investment in knowledge infrastructure. <i>Communications ofthe ACM, </i>3(11).</p><p>Maedche, Alexander and Steffen Staab. 2000. Semi-automatic engineering of ontologies from text. In <i>Proceedings ofthe 12th International Conference on Software Engineering and Knowledge Engineering (SEKE'2000), </i>Chicago, IL.</p><p>Maedche, Alexander and Steffen Staab 2001. Ontology learning for the semantic web.</p><p><i>IEEE Intelligent Systems, </i>16(2): 72-79.</p><p>Magnini, Bernardo and Gabriella Cavaglia. 2000. Integrating subject field codes into WordNet. In <i>Proceedings ofthe second International Conference on Language Resources and Evaluation (LREC2000), </i>Atenes.</p><p>Missikoff, Michele and X.F. Wang. 2001. Consys—A group decision-making support system for collaborative ontology building. In <i>Proceedings of Group Decision &amp; Negotiation 2001 Conference, </i>La Rochelle, France.</p><p>Navigli, Roberto, and Paola Velardi. 2003. An analysis of ontology-based query expansion strategies. <i>Workshop on Adaptive Text Extraction and Mining, </i>held in conjunction with ECML 2003, Cavtat</p><p>Dubrovnik, Croatia, September 22.</p><p>Navigli, Roberto, Paola Velardi, Alessandro Cucchiarelli, and Francesca Neri. 2004. Extending and enriching WordNet with OntoLearn. In Second <i>Global WordNet Conference, </i>Brno, Czech Republic, January 20-23. Springer-Verlag.</p><p>Navigli, Roberto, Paola Velardi, and Aldo Gangemi. 2003. Corpus driven ontology learning: A method and its application to automated terminology translation, <i>IEEE Intelligent Systems, </i>18(1): 11-27.</p><page local="29" global="179"/><p>Oltramari, Alessandro, Aldo Gangemi, Nicola Guarino, and Claudio Masolo. 2002. Restructuring WordNet's top-level: The OntoClean approach. In <i>Proceedings of the International Conference on Language Resources and Evaluation (LREC2002), </i>Las Palmas, Spain.</p><p>Smith, Barry and Christopher A. Welty. 2001. Ontology: Towards a new synthesis. <i>Formal Ontology in Information Systems,</i></p><p>ACM Press.</p><p>Sowa, John F. 1984. <i>Conceptual Structures: Information Processing in Mind and Machine. </i>Addison-Wesley, Reading, MA.</p><p>Uschold, Mike and Michael Gruninger. 1996. Ontologies: Principles, methods and applications. <i>Knowledge Engineering Review, </i>11(2).</p><p>Velardi, Paola, Michele Missikoff, and Roberto Basili. 2001. Identification of relevant terms to support the construction of domain ontologies. In <i>ACL-EACL Workshop on Human Language Technologies, </i>Toulouse, France, July.</p><p>Vossen, Piek, editor. 1998. <i>EuroWordNet: A</i> <i>Multilingual Database with Lexical Semantic Networks.</i><i> </i>Kluwer Academic, Dordrecht, Netherlands.</p><p>Vossen, Piek. 2001. Extending, trimming and fusing WordNet for technical documents. In <i>NAACL 2001 Workshop on WordNet and Other Lexical Resources, </i>Pittsburgh, July.</p><p>Yamamoto, Mikio and Kenneth W. Church. 2001. Using suffix arrays to compute term frequency and document frequency for all substrings in a corpus. <i>Computational Linguistics, </i>27(1): 1-30.</p><p>Yokoi, Toshio. 1993. The EDR electronic dictionary. <i>Communications ofthe ACM,</i> 38(11): 42-44.</p></references><appendix title="Appendix"><doubt alpha="57.1" length="14" tooSmall="False" monospace="0.0">{ activity%1 }</doubt><doubt alpha="40.0" length="10" tooSmall="False" monospace="0.0">{ work%1 }</doubt><doubt alpha="36.4" length="22" tooSmall="False" monospace="0.0">{ project:00508925%n }</doubt><doubt alpha="51.7" length="29" tooSmall="False" monospace="0.0">{ tourismproject:00193473%n }</doubt><doubt alpha="52.9" length="34" tooSmall="False" monospace="0.0">{ ambitious_project:007111130/oa }</doubt><doubt alpha="36.4" length="22" tooSmall="False" monospace="0.0">{ service:00379388%n }</doubt><page local="27" global="177"/><doubt alpha="57.1" length="28" tooSmall="False" monospace="0.0">{ traveLservice:00l9l846%n }</doubt><doubt alpha="40.0" length="30" tooSmall="False" monospace="0.0">{ air_service#2:00202658°/on }</doubt><doubt alpha="49.2" length="61" tooSmall="False" monospace="0.0">{ ai^_service#4:00l94802%n } { transport_service:007l604l%n }</doubt><doubt alpha="50.0" length="30" tooSmall="False" monospace="0.0">{ ferry_service#2:007l7l67%n }</doubt><doubt alpha="48.4" length="184" tooSmall="False" monospace="0.0">{ expres^_service#3:007l6943%n } { exchang^_service:024l3424%n } { guid^service:04840928%n } { restauran^service:03233732%n } { raiLservice:03207559%n } { customer_service:07l97309%n }</doubt><doubt alpha="48.1" length="27" tooSmall="False" monospace="0.0">{ gues^service:0730492l%n }</doubt><doubt alpha="45.2" length="31" tooSmall="False" monospace="0.0">{ regula^service#2:07525988%n }</doubt><doubt alpha="56.4" length="101" tooSmall="False" monospace="0.0">{ outstanding^ustomer_service:0223274l%a } { tourismservice:00l93473%n } { waite^service:0767l545%n }</doubt><doubt alpha="55.3" length="190" tooSmall="False" monospace="0.0">{ regula^_service:02255650%a,schedule^_service:02255439%a } { personalized_service:0l703424%a,peisonal_service:0l702632%a } { secretariaLservice:0260l509%a } { religiou^_service:0272l678%a }</doubt><doubt alpha="48.8" length="121" tooSmall="False" monospace="0.0">{ churc^_service:006669l2%n } { variou^_service:00462055%a } { helpfuLservice:02376874%a } { quality_service:037l4294%n }</doubt><doubt alpha="42.6" length="54" tooSmall="False" monospace="0.0">{ ai^service#3:037l6758%n } { roomservice:03250788%n }</doubt><doubt alpha="43.6" length="179" tooSmall="False" monospace="0.0">{ mai^_service:07387889%n } { laundr^_service:029ll395%n } { ca^service#5:02364995%n } { hou^roo^_service:l0938063%n } { transpor^_service#2:02495376%n } { ca^service:02383458%n }</doubt><doubt alpha="47.2" length="123" tooSmall="False" monospace="0.0">{ bu^service#2:0235687l%n } { taxLservice:0236l877%n } { coac^service#2:02459686%n } { publi^transpor^_service:03l84373%n }</doubt><doubt alpha="45.8" length="142" tooSmall="False" monospace="0.0">{ bu^service:02356526%n,coac^service:02356526%n } { expres^_service#2:026534l4%n } { locaLbu^service:0l056664%a } { trai^_service:03528724%n }</doubt><doubt alpha="41.4" length="58" tooSmall="False" monospace="0.0">{ expres^_service:02653278%n } { ca^service#2:02384604%n }</doubt><doubt alpha="41.1" length="56" tooSmall="False" monospace="0.0">{ coac^service#3:03092927%n } { boa^service:02304226%n }</doubt><doubt alpha="50.0" length="28" tooSmall="False" monospace="0.0">{ ferry_service:0267l945%n }</doubt><doubt alpha="44.1" length="59" tooSmall="False" monospace="0.0">{ car-ferr^_service:02388365%n } { ai^_service:052704l7%n }</doubt><doubt alpha="48.3" length="29" tooSmall="False" monospace="0.0">{ suppor^service:05272723%n }</doubt><page local="28" global="178"/></appendix></body></article>