<?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" global="272"/><title>MARS: A Specialized RTE System for Parser Evaluation</title><pubinfo>Proceedings of the 5th International Workshop on Semantic Evaluation, ACL 2010,pages 272-275, Uppsala, Sweden, 15-16 July 2010. ©2010 Association for Computational Linguistics</pubinfo><author surname="Wang" givenname="Rui"><org  name="Saarland University" country="Germany" city="Saarbrucken"/></author><author surname="Zhang" givenname="Yi"><org  name="Saarland University" country="Germany" city="Saarbrucken"/></author></firstpageheader><frontmatter><p><b>MARS: A Specialized RTE System for Parser Evaluation</b></p><p><b>Rui Wangt      Yi Zhangt*</b></p><p><b>I </b>Department of Computational Linguistics, Saarland University <b><i>X </i></b>LT-Lab, German Research Center for Artificial Intelligence Im Stadtwald, 66123 Saarbrücken, Germany</p><p>{rwang,yzhang}@coli.uni-sb.de</p></frontmatter><abstract>This paper describes our participation in the the SemEval-2010 Task #12, <i>Parser Evaluation using Textual Entail­ment. </i>Our system incorporated two depen­dency parsers, one semantic role labeler, and a deep parser based on hand-crafted grammars. The shortest path algorithm is applied on the graph representation of the parser outputs. Then, different types of features are extracted and the entail­ment recognition is casted into a machine-learning-based classification task. The best setting of the system achieves 66.78% of accuracy, which ranks the 3rd place. </abstract></header><body><section number="1" title="Introduction"><p>The SemEval-2010 Task #12, <i>Parser Evaluation using Textual Entailment </i>(PETE) (Yuret et al., 2010), is an interesting task connecting two areas of research, parsing and recognizing textual entail­ment (RTE) (Dagan et al., 2005). The former is usually concerned with syntactic analysis in spe­cific linguistic frameworks, while the latter is be­lieved to involve more semantic aspects of the hu­man languages. However, no clear-cut boundary can be drawn between syntax and semantics for both tasks. In recent years, the parsing commu­nity has been reaching beyond what was usually accepted as syntactic structures. Many deep lin­guistic frameworks allow the construction of se­mantic representations in parallel to the syntactic structure. Meanwhile, data-driven shallow seman­tic parsers (or semantic role labelers) are another popular type of extension to enrich the information in the parser outputs.</p><p>Although <i>entailment </i>is described as a semantic relation, RTE, in practice, covers linguistic phe­nomena at various levels, from surface text to the meaning, even to the context and discourse. One proposal of solving the problem is to deal with dif­ferent cases of entailment using different special­ized RTE modules (Wang and Neumann, 2009). Then, the PETE data can be naturally classified into the syntactic and shallow semantic categories.</p><p>By participating in this shared task, we aim to investigate whether different parsing outputs leads to different RTE accuracy, and on the contrary, whether the "application"-based evaluation pro­vides insights to the parser comparison. Further, we investigate if strict grammaticality checking with a linguistic grammar is helpful in this task.</p></section><section number="2" title="System Description"><p>The workflow of the system is shown in Figure 1 and the details of the three components will be elaborated on in the following sections.</p><subsection number="2.1" title="Preprocessing"><p>In this paper, we generally refer all the linguistic analyses on the text as <i>preprocessing. </i>The output of this procedure is a graph representation, which approximates the meaning of the input text. In par­ticular, after tokenization and POS tagging, we did dependency parsing and semantic role labeling. In addition, HPSG parsing is a filter for ungrammat-ical hypotheses.</p><p><b>Tokenization and POS Tagging   </b>We use the</p><p>Penn Treebank style tokenization throughout the various processing stages. <b>TnT, </b>an HMM-based POS tagger trained with Wall Street lournal sec­tions of the PTB, was used to automatically pre­dict the part-of-speech of each token in the texts and hypotheses.</p><p><b>Dependency Parsing </b>For obtaining the syntac­tic dependencies, we use two dependency parsers, MSTParser (McDonald et al., 2005) and Malt-Parser (Nivre et al., 2007). MSTParser is a graph-based dependency parser where the best parse tree is acquired by searching for a spanning tree<page local="2" global="273"/></p><p>! Preprocessing</p><p><b>I </b>Feature-based Classification</p><p>fc£ Yes/No</p><doubt alpha="100.0" length="1" tooSmall="False" monospace="0.0">y</doubt><doubt alpha="100.0" length="2" tooSmall="False" monospace="0.0">No</doubt><p>Figure 1 : Workflow of the System which maximize the score on an either partially or fully connected dependency graph. MaltParser is a transition-based incremental dependency parser, which is language-independent and data-driven. It contains a deterministic algorithm, which can be viewed as a variant of the basic shift-reduce al­gorithm. Both parsers can achieve state-of-the-art performance and Figure 2 shows the resulting syn­tactic dependency trees of the following T-H pair,</p><p>ID: <i>2036; </i>Entailment: <i>YES</i> <b>T:</b><b> </b><i>Devotees of the market question the value of</i></p><p><i>the work national service would perform. </i>H: <i>Value is questioned.</i></p><p><b>Semantic Role Labeling </b>The statistical depen­dency parsers provide shallow syntactic analyses of the entailment pairs through the limited vocab­ulary of the dependency relations. In our case, the CoNLL shared task dataset from 2008 were used to train the statistical dependency parsing mod­els. While such dependencies capture interesting syntactic relations, when compared to the parsing systems with deeper representations, the contained information is not as detailed. To compensate for this, we used a shallow semantic parser to predict the semantic role relations in the <b>T </b>and <b>H </b>of en­tailment pairs. The shallow semantic parser was also trained with CoNLL 2008 shared task dataset, with semantic roles extracted from the Propbank and Nombank annotations (Zhang et al., 2008). Figure 3 shows the resulting semantic dependency graphs of the T-H pair.</p><p><b>HPSG Parsing </b>We employ the English Re­source Grammar (Flickinger, 2000), a hand­written linguistic grammar in the framework of HPSG, and the PET HPSG parser (Callmeier, 2001) to check the grammaticality of each hy­pothesis sentence. As the hypotheses in this PETE shared task were automatically generated, some ungrammatical hypotheses occur in non-entailment pairs, the grammaticality checking al­lows us to quickly identify these instances.</p></subsection><subsection number="2.2" title="Dependency Path Extraction"><p>According to the task definition, we need to ver­ify whether those dependency relations in H also appear in T. We firstly find out all the impor­tant dependency triples in H, like &lt;word, depen­dency relation, word&gt;, excluding those having stop words. The extracted syntactic dependency triples of the example T-H pair would be none, since the only content words "value" and "ques­tioned" have no direct syntactic dependency in-between (Figure 2). The extracted semantic de­pendency triples would be &lt;"questioned", "Al", "value"&gt; (Figure 3).</p><p>After that, we use the word pairs contained in the extracted dependency triples as anchors to find out the corresponding dependency relations in T. Notice that it is not necessarily that we can al­ways find a direct dependency relation in T be­tween the same word pair, so we need to traverse the dependency tree or graph to find the <i>depen­dency paths. </i>In general, we treat all the depen­dency trees and graphs as undirected graphs with loops, but keep records for the directions of the edges we traverse. For the following three repre­sentations, we apply slightly different algorithms to find the dependency path between two words,</p><p><b>Syntactic Dependency Tree </b>We simply traverse the tree and find the corresponding depen­dency path connecting the two words;</p><p><b>Semantic Dependency Graph </b>We apply Dijk-stra's algorithm (Dijkstra, 1959) to find the shortest path between the two words;</p><p><b>Joint Dependency Graph </b>We assign different weights to syntactic and semantic dependen­cies and apply Dijkstra's algorithm to find the shortest path (with the lowest cost)<footnote anchor="1"/>.</p></subsection><subsection number="2.3" title="Feature-based Classification"><p>Based on the meaning representation we have dis­cussed above (Section 2.1 and Section 2.2), we ex-</p><p>!In practice, we simply give semantic dependencies 0.5 cost and syntactic dependencies 1.0 cost, to show the prefer­ences on the former when both exist.</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>Feature</p></td><td class="cell"><p></p></td><td class="cell"><p>S VM-based</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p>Extraction</p></td><td class="cell"><p><b>--&gt;</b></p></td><td class="cell"><p>Classification</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="3" global="274"/><doubt alpha="66.7" length="6" tooSmall="False" monospace="0.0">-Root-</doubt><doubt alpha="50.0" length="2" tooSmall="False" monospace="0.0">T:</doubt><p><b>Devotees of</b> <b>devotee of</b> <b>market question</b></p><doubt alpha="0.0" length="3" tooSmall="False" monospace="0.0">1 2</doubt><doubt alpha="83.3" length="6" tooSmall="False" monospace="0.0">NNS IN</doubt><doubt alpha="100.0" length="1" tooSmall="False" monospace="0.0">n</doubt><doubt alpha="60.0" length="5" tooSmall="False" monospace="0.0">the 3</doubt><doubt alpha="83.3" length="6" tooSmall="False" monospace="0.0">the DT</doubt></subsection></section><section number="4" title="5 market question NN NN"><doubt alpha="22.7" length="22" tooSmall="True" monospace="0.0">ROOT        \  ✓---P \</doubt><p><b>-Root-   Value    is questioned</b> <b>value    be question</b> <b>Devotees 1</b> <b>devotee NNS</b> <b>value NNP</b> <b>market 4</b> <b>market NN</b> <b>questioned</b> <b>question VBN</b> <b>question</b> <b>question NN</b> <b>value NN</b> <b>service 12</b> <b>service NN</b> <b>would MD</b> <b>perform VB</b></p><doubt alpha="0.0" length="4" tooSmall="False" monospace="0.0">1234</doubt><doubt alpha="58.8" length="17" tooSmall="False" monospace="0.0">H;NNP     VBZ VBN</doubt><doubt alpha="12.5" length="8" tooSmall="False" monospace="0.0">I*5*55!\</doubt><doubt alpha="62.5" length="40" tooSmall="False" monospace="0.0">the   value   of the 6 7 the value DT NN</doubt><figure caption="Figure 2: Syntactic dependency of the example T-H pair by MaltParser."></figure><doubt alpha="50.0" length="2" tooSmall="False" monospace="0.0">H:</doubt><doubt alpha="100.0" length="1" tooSmall="False" monospace="0.0">r</doubt><doubt alpha="71.4" length="7" tooSmall="False" monospace="0.0">Value 1</doubt><doubt alpha="50.0" length="4" tooSmall="False" monospace="0.0">of 2</doubt><doubt alpha="80.0" length="5" tooSmall="False" monospace="0.0">of IN</doubt><doubt alpha="100.0" length="2" tooSmall="True" monospace="0.0">Al</doubt><doubt alpha="50.0" length="4" tooSmall="False" monospace="0.0">is 2</doubt><doubt alpha="83.3" length="6" tooSmall="False" monospace="0.0">be VBZ</doubt><doubt alpha="50.0" length="2" tooSmall="False" monospace="0.0">"I</doubt><doubt alpha="100.0" length="2" tooSmall="False" monospace="0.0">nr</doubt><doubt alpha="60.0" length="5" tooSmall="False" monospace="0.0">the 6</doubt><doubt alpha="71.4" length="7" tooSmall="False" monospace="0.0">value 7</doubt><doubt alpha="100.0" length="2" tooSmall="False" monospace="0.0">of</doubt><doubt alpha="0.0" length="1" tooSmall="False" monospace="0.0">8</doubt><doubt alpha="100.0" length="2" tooSmall="False" monospace="0.0">IN</doubt><doubt alpha="60.0" length="5" tooSmall="False" monospace="0.0">the 9</doubt><doubt alpha="57.1" length="7" tooSmall="False" monospace="0.0">work 10</doubt><doubt alpha="85.7" length="7" tooSmall="False" monospace="0.0">work NN</doubt><doubt alpha="100.0" length="2" tooSmall="False" monospace="0.0">JU</doubt><doubt alpha="83.3" length="6" tooSmall="True" monospace="0.0">AM-LOC</doubt><doubt alpha="100.0" length="5" tooSmall="False" monospace="0.0">would</doubt><doubt alpha="0.0" length="2" tooSmall="False" monospace="0.0">13</doubt><doubt alpha="100.0" length="7" tooSmall="False" monospace="0.0">perform</doubt><doubt alpha="0.0" length="2" tooSmall="False" monospace="0.0">15</doubt><figure caption="Figure 3: Semantic dependency of the example T-H pair by MaltParser and our SRL system."></figure><p>tract features for the machine-learning-based clas­sifier. First of all, we should check whether there are dependency triples extracted from H, other­wise for our system, there is no meaning repre­sentation for that sentence. Then we also need to check whether the same words can be found in T as well. Only if the corresponding dependency paths are successfully located in T, we could ex­tract the following features.</p><p>The direction of each dependency relation or path could be interesting. The direction of the H-path is clear, so we only need to check the direction of the T-path. In practice, we simply use a boolean value to represent whether T-path contains dependency relations with different di­rections. For instance, in Figure 3, if we extract the path from "market" to "value", the directions of the dependency relations contained in the path would be &lt;— and —&gt;, one of which would be incon­sistent with the dependency relation in H.</p><p>Notice that all the dependency paths from H have length l<footnote anchor="2"/>, but the lengths of the dependency paths from T are varied. If the latter length is also 1, we can simply compare the two dependency re­lations; otherwise, we compare each of the dependency relation contained the T-path with H-path one by one<footnote anchor="3"/>. By comparison, we mainly focus on two values, the category of the dependency rela­tion (e.g. syntactic dependency vs. semantic de­pendency) and the content of the dependency rela­tion (e.g. Al vs. AM-LOC).</p><footnote label="2">The length of one dependency path is defined as the num­ber of dependency relations contained in the path.</footnote><p>We also incorporate the string value of the de­pendency relation pair and make it boolean ac­cording to whether it occurs or not. Table 1 shows the feature types we extract from each T-H pair.</p></section><section number="3" title="Experiments"><p>As we mentioned in the preprocessing section (Section 2.1), we utilize the open source depen­dency parsers, MSTParser<footnote anchor="4"/> and MaltParser<footnote anchor="5"/>, our own semantic role labeler (Zhang et al., 2008), and the PET HPSG parser<footnote anchor="6"/>. For the shortest path algo­rithm, we use the jGraphT package<footnote anchor="7"/>; and for the machine learning toolkit, we use the UniverSVM</p><footnote label="3">Enlightened by Wang and Neumann (2007), we ex­clude some dependency relations like "CONJ", "COORD", "APPO", etc., heuristically, since in most of the cases, they will not change the relationship between the two words at both ends of the path.</footnote><footnote label="4">http://sourceforge.net/projects/ mstpar serf</footnote><p>http ://maltparser.org/</p><footnote label="6">http://heartofgold.dfki.de/PET.html</footnote><footnote label="7">http://jgrapht.sourceforge.net/</footnote><p><b>nation11</b><page local="4" global="275"/></p><doubt alpha="100.0" length="6" tooSmall="False" monospace="0.0">nation</doubt><p>Table 1 : Feature types of different settings of the system. <i>H_Null? </i>means whether H has dependencies; <i>TJVull? </i>means whether T has the corresponding paths (us­ing the same word pairs found in H); <i>Dir </i>is whether the di­rection of the path T the same as H; <i>Multi? </i>adds a prefix, ra_, to the <i>Rel_Pair </i>features, if the T-path is longer than one dependency relation; <i>DepJSame ? </i>checks whether the two de­pendency types are the same, i.e. syntactic and semantic de­pendencies; <i>RelSim? </i>only occurs when two semantic depen­dencies are compared, meaning whether they have the same prefixes, e.g. <i>C-, AM-, </i>etc.; <i>RelSame? </i>checks whether the two dependency relations are the same; and <i>Rel-Pair </i>simple concatenates the two relation labels together. Notice that, the first seven feature types all contain boolean values, and for the last one, we make it boolean as well, by observing whether that pair of dependency labels appear or not.</p><p>package<footnote anchor="8"/>. We test different dependency graphs and feature sets as mentioned before (Table 1), and the results are shown in Table 2.</p><p>First of all, in almost all the cases, the grammat­icality checking based on HPSG parsing is help­ful, if we compare each pair of results at the two rows, +GC and -GC. In all cases, the joint graph representation achieves better results. This in­dicates that features extracted from both syntac­tic dependency and shallow semantic dependency are useful for the entailment recognition. For the MaltParser case, the semantic features show great importance. Notice that the performance of the whole system does not necessarily reflect the per­formance of the parser itself, since it also depends on our entailment modules. In all, the best setting of our system ranks the 3rd place in the evaluation.</p></section><section number="4" title="Conclusion"><p>In this paper, we present our system used in the PETE task, which consists of preprocessing, de­pendency path extraction, and feature-based clas­sification. We use MSTParser and MaltParser as dependency parsers, our SRL system as a shallow semantic parser, and a deep parser based on hand­crafted grammars for grammaticality checking. The entailment recognition is done by an SVM-based classifier using features extracted from the graph representation of the parser outputs. Based on the results, we tentatively conclude that both the syntactic and the shallow semantic features are useful. A detailed error analysis would be our on­going work in the near future.</p><footnote label="8">http://www.kyb.mpg.de/bs/people/ fabee/universvm.html</footnote><p><b>Acknowledgment</b></p><p>The authors thank the PIRE PhD scholarship and the German Excellence Cluster of MMCI for the support of the work.</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><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"><p>H_Null?</p></td><td class="cell"><p>T_Null?</p></td><td class="cell"><p>S</p></td><td class="cell"><p>Multi?</p></td><td class="cell"><p>Dep_Same?</p></td><td class="cell"><p>ReLSim?</p></td><td class="cell"><p>ReLSame?</p></td><td class="cell"><p>ReLPair</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p>Joint</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>No Sem</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>No Syn</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></tr></table><table caption="Table 2: Experiment results of our system with different settings." 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></p></td><td class="cell"><p>MSTParser+SRL</p></td><td class="cell"><p>MaltParser+SRL</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p>Joint</p></td><td class="cell"><p>No Sem</p></td><td class="cell"><p>No Syn</p></td><td class="cell"><p>Joint</p></td><td class="cell"><p>No Sem</p></td><td class="cell"><p>No Syn</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p><b>+GC</b></p></td><td class="cell"><p>0.5249</p></td><td class="cell"><p>0.5116 (-1.3%)</p></td><td class="cell"><p>0.5050 (-2.0%)</p></td><td class="cell"><p>0.6678</p></td><td class="cell"><p>0.5282 (-14.0%)</p></td><td class="cell"><p>0.6346 (-3.3%)</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p><b>-GC</b></p></td><td class="cell"><p>0.5216</p></td><td class="cell"><p>0.5050</p></td><td class="cell"><p>0.4950</p></td><td class="cell"><p>0.6545</p></td><td class="cell"><p>0.5282</p></td><td class="cell"><p>0.6179</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></section><references><p>Ulrich Callmeier. 2001. Efficient parsing with large-scale unification grammars. Master's thesis, Universität des Saarlandes, Saarbrücken, Germany.</p><p>Ido Dagan, Oren Glickman, and Bernardo Magnini. 2005. The pascal recognising textual entailment challenge. In Quinonero-Candela et al., editor, <i>MLCW 2005, </i>volume LNAI Volume 3944, pages 177-190. Springer-Verlag.</p><p>E. W. Dijkstra. 1959. A note on two problems in connexion with graphs. <i>Numerische Mathematik, </i>1:269-271.</p><p>Dan Flickinger. 2000. On building a more efficient gram­mar by exploiting types. <i>Natural Language Engineering, </i>6(l):15-28.</p><p>Ryan McDonald, Fernando Pereira, Kiril Ribarov, and Jan Hajic. 2005. Non-Projective Dependency Parsing us­ing Spanning Tree Algorithms. In <i>Proceedings of HLT-EMNLP 2005, </i>pages 523-530, Vancouver, Canada.</p><p>Joakim Nivre, Jens Nilsson, Johan Hall, Atanas Chanev, Gülsen Eryigit, Sandra Kubier, Svetoslav Marinov, and Erwin Marsi. 2007. Maltparser: A language-independent system for data-driven dependency parsing. <i>Natural Lan­guage Engineering, </i>13(1 ): 1—41.</p><p>Rui Wang and Günter Neumann. 2007. Recognizing textual entailment using a subsequence kernel method. In <i>Pro­ceedings of AAAl-07, </i>Vancouver, Canada, July.</p><p>Rui Wang and Günter Neumann. 2009. An accuracy-oriented divide-and-conquer strategy for recognizing tex­tual entailment. In <i>Proceedings of TAC 2008, </i>Gaithers-burg, Maryland, USA.</p><p>Deniz Yuret, Ay din Han, and Zehra Turgut. 2010. Semeval-2010 task 12: Parser evaluation using textual entailments. In <i>Proceedings of the SemEval-2010 Evaluation Exercises on Semantic Evaluation.</i></p><p>Yi Zhang, Rui Wang, and Hans Uszkoreit. 2008. Hybrid learning of dependency structures from heterogeneous lin­guistic resources. In <i>Proceedings of the Twelfth Con­ference on Computational Natural Language Learning (CoNLL 2008), </i>pages 198-202, Manchester, UK.</p></references></body></article>