<?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="245"/><title>NAIST.Japan: Temporal Relation Identification Using Dependency Parsed Tree</title><pubinfo>Proceedings of the 4th International Workshop on Semantic Evaluations (SemEval-2007),pages 245-248, Prague, June 2007. ©2007 Association for Computational Linguistics</pubinfo><author surname="Cheng" givenname="Yuchang"><org  name="Nara Institute of Science and Technology" country="Japan" city="Nara"/></author><author surname="Asahara" givenname="Masayuki"><org  name="Nara Institute of Science and Technology" country="Japan" city="Nara"/></author><author surname="Matsumoto" givenname="Yuji"><org  name="Nara Institute of Science and Technology" country="Japan" city="Nara"/></author></firstpageheader><frontmatter><p><b>NAIST.Japan: Temporal Relation Identification Using Dependency Parsed</b></p><p><b>Tree</b></p><p><b>Yuchang Cheng, Masayuki Asahara and Yuji Matsumoto</b></p><p>Graduate School oflnformatino Science, Nara Institute of Science and Technology 8916-5 Takayama, Ikoma, Nara, 630-0192, Japan {yuchan-c, masayu-a, matsu}@is.naist.jp</p></frontmatter><abstract>In this paper, we attempt to use a sequence labeling model with features from depen­dency parsed tree for temporal relation iden­tification. In the sequence labeling model, the relations of contextual pairs can be used as features for relation identification of the current pair. Head-modifier relations be­tween pairs of words within one sentence can be also used as the features. In our pre­liminary experiments, these features are ef­fective for the temporal relation identifica­tion tasks. </abstract></header><body><section number="1" title="Overview of our system"><p>This paper presents a temporal relation identifier by the team NAIST.Japan. Our identifier has two char-actaristics: sequence labeling model and use of de­pendency parsed tree.</p><p>Firstly, we treated each problem a sequence la­beling problem, such that event/time pairs were or­dered by the position of the events and times in the document. This idea is for task B and C. In task B, the neighbouring relations between an EVENT and DCT-TIMEX3 tend to interact. In task C, when EVENT-a, EVENT-b, and EVENT-c are linearly or­dered, the relation between EVENT-a and EVENT-b tends to affect the one between EVENT-b and</p><p>EVENT-c.</p><p>Secondly, we introduced dependency features where each word was annotated with a label indi­cating its tree position to the event and the time, e.g. "descendant" of the event and "ancestor" of the time.</p><p>The dependency features are introduced for our ma­chine learning-based relation identifier. In task A, we need to label several different event-time pairs within the same sentence. We can use information from TIMEX3, which is a descendent of the target EVENT in the dependency tree.</p><p>Section 2 shows how to use a sequence labeling model for the task. Section 3 shows how to use the dependency parsed tree for the model. Section 4 presents the results and discussions.</p></section><section number="2" title="Temporal Relation Identification by Sequence Labeling"><p>Our approach to identify temporal relation is based on a sequence labeling model. The target pairs are linearly ordered in the texts.</p><p>Sequence labeling model can be defined as a method to estimate an optimal label sequence</p><p>over an observed sequence <i>{xi,</i><i> xii</i><i>xn).</i><i> </i>We consider, w-parameterized function</p><doubt alpha="58.8" length="34" tooSmall="False" monospace="0.0">f(x)= argmaxF(i,y;w)= argmax{w,y)}</doubt><p>Here, denotes all possible label combinations over <i>y;</i><i> &lt;!&gt;(x,y) </i>denotes a feature expression over <i>x,</i><i> </i><i>y.</i><i> </i>Introducing a kernel function:</p><doubt alpha="29.0" length="31" tooSmall="False" monospace="0.0">K((x,y),(x,y))={®(x,y),®(x,y)),</doubt><p>we have a dual representation:</p><doubt alpha="100.0" length="1" tooSmall="False" monospace="0.0">m</doubt><doubt alpha="35.7" length="28" tooSmall="False" monospace="0.0">F(x,y)=^aiÄ-((x«,y«),(x,y)),</doubt><doubt alpha="66.7" length="3" tooSmall="False" monospace="0.0">i=l</doubt><page local="2" global="246"/><p>given a training data set</p><doubt alpha="30.6" length="36" tooSmall="False" monospace="0.0">{(x(1),y(1)),...,(x(m),y(m))}.We use</doubt><p>HMM_SVM (Altun et al., 2003) as the sequence labeling model, in which the training is performed to maximize a margin <i>7.</i><i></i><i> </i><i>=</i><i> </i><i>F(xik\f/k))</i><i> </i><i>-</i><i> </i>max <i>F(x{k\y).</i></p><doubt alpha="75.0" length="4" tooSmall="False" monospace="0.0">y^yW</doubt><p>The sequence labeling approach is natural for task B and C. In task B, if a document is about affairs in the past, the relations between events and a docu­ment creation time tend to be "BEFORE". All rela­tions in task B depend on each other. In task C, if a relation between the preceding event and the current one is "AFTER", the current one is in the past. The information helps to determine the relation between the current and succeeding one. Whereas we have reasonable explanation to introduce sequence label­ing for task B and C, we cannot for task A. However, in our preliminary experiments with trial data, the sequence labeling model outperformed point-wise models for task A. Thus, we introduce the sequence labeling model for task A.</p><p>Now, we present the sequence labeling approach for each task in detail by figure 1, 2 and 3. The left parts of figures are the graphical models of the sequence labeling. The right parts are the tagged corpus: (S) and (/S) are sentence boundaries; a EVENT-«« denotes an EVENT; a TIME-«« de­notes a TIMEX3; a TIME-DCT in figure 2 de­notes a TIMEX3 with document creation time; a boxed EVENT-«« in figure 3 denotes a matrix verb</p><p>EVENT.</p><p>For task A (figure 1), ce is a sequence of pairs be­tween an EVENT and a TIMEX3 within the same sentence. is a sequence ofcorresponding relations. Event-time pairs are ordered first by sentence posi­tion, then by event position and finally by time posi­tion. For task B (figure 2), ce is a sequence of pairs between an EVENT and a DCT-TIMEX3. is a se­quence of corresponding relations. All pairs in the same text are linearly ordered and connected. For task C (figure 3), ce is a sequence of pairs between two matrix verb EVENTs in the neighboring sen­tences. is a sequence of corresponding relations. All pairs in the same text are linearly ordered and connected, even if the two relations are not in the adjacent sentences.</p><doubt alpha="100.0" length="2" tooSmall="False" monospace="0.0">yx</doubt><doubt alpha="33.3" length="3" tooSmall="True" monospace="0.0">&lt;s&gt;</doubt><doubt alpha="46.9" length="49" tooSmall="True" monospace="0.0">IVINI 0I"IIMI 01      ivINI 01    IIMI 01 IIMI 02</doubt><doubt alpha="60.9" length="23" tooSmall="False" monospace="0.0">IVINI 01^IIMI 02IVINI02</doubt><doubt alpha="25.0" length="4" tooSmall="True" monospace="0.0">&lt;/S&gt;</doubt><doubt alpha="43.8" length="16" tooSmall="True" monospace="0.0">EVENÏ 02«71ME 01</doubt><p><b>EVEN™2</b>o-n<b>ME_02 ™E_03.........EVENub....</b></p><doubt alpha="25.0" length="4" tooSmall="True" monospace="0.0">&lt;/s&gt;</doubt><doubt alpha="38.5" length="13" tooSmall="True" monospace="0.0">EVEN^03«™e_03</doubt><figure caption="Figure 1: Sequence Labeling Model for Task A"></figure><doubt alpha="33.3" length="3" tooSmall="True" monospace="0.0">&lt;S&gt;</doubt><doubt alpha="92.9" length="14" tooSmall="True" monospace="0.0">EVENUMo^MEjDCT</doubt><doubt alpha="25.0" length="8" tooSmall="True" monospace="0.0">&lt;/s&gt; &lt;s&gt;</doubt><doubt alpha="59.1" length="22" tooSmall="False" monospace="0.0">...EVENTJR.. ...EVENUS</doubt><figure caption="Figure 2: Sequence Labeling Model for Task B"></figure><p><b>Before </b><b>|~H~I </b><b>evewtji</b>o<b>evewmb</b> <b>After    </b><b>r"H~l </b><b>EVEINIJ03</b><b>0</b><b>EVEINL04</b> <b>Overlap</b><b>rTn </b><b>evewtjm</b>o<b>evemjk</b></p><doubt alpha="46.2" length="13" tooSmall="True" monospace="0.0">|EVEWTJ)1|...</doubt><doubt alpha="50.0" length="12" tooSmall="True" monospace="0.0">...[EVENOl..</doubt><doubt alpha="34.3" length="35" tooSmall="True" monospace="0.0">...IEVEWT 04|...............EVEWTJ5</doubt><doubt alpha="66.7" length="12" tooSmall="True" monospace="0.0">...lEVEINr C</doubt><figure caption="Figure 3: Sequence Labeling Model for Task C"></figure></section><section number="3" title="Features from Dependency Parsed Tree"><p>A dependency relation is a head-modifier relation on a syntactic tree. Figure 4 shows an example de­pendency parsed tree of the following sentence -<i>"The warremts may be exercised uritil 90 days after their issue date". </i>We parsed the TimeEval data us­ing MSTParser v0.2 (McDonald and Pereira, 2006), which is trained with all Penn Treebank (Marcus et al., 1993) without dependency label.</p><p>We introduce <b>tree position </b>labels between an tar­get node and another node on the dependency parsed tree: ANC (ancestor), DES (descendant), SIB (sib­ling), and TARGET (target word). Figure 5 shows the labels, in which the box with double lines is the target node. The tree position between the target EVENT and a word in the target TIMEX3 is used as a feature for our machine learning-based relation identifier.</p><p>We also use the words in the sentence including the target entities as features. Each word is anno-<page local="3" global="247"/></p><figure caption="Figure 4: An example of dependency parsed tree Figure 5: Tree position labels"></figure><p>TARGET node: <i>"exercised^ </i>TARGET nodes: "90" and <i>"days"    </i>TARGET-A node: <i>"exercised^</i></p><doubt alpha="61.3" length="31" tooSmall="False" monospace="0.0">TARGET-B nodes: "90" and "days"</doubt><doubt alpha="59.5" length="42" tooSmall="False" monospace="0.0">(1) EVENT-based (2) TIMEX3-based (3) JOINT</doubt><figure caption="Figure 6: Tree position labels on the example dependency parsed tree"></figure><p>tated with (1) its tree position to the EVENT, (2) its tree position to the TIMEX3, and (3) the com­bination of the labels from (1) and (2). Fig. 6 shows the labels of tree positions. The left picture shows (1) EVENT-based labels of the tree position with the target EVENT <i>"exercised". </i>The center pic­ture shows (2) TIMEX3-based ones with the target</p><p>TIMEX3 <i>"90 days". </i>The right picture shows (3)</p><p>JOINT ones which are combinations of the relation label with the EVENT and with the TIMEX3. We perform feature selection on the words in the cur­rent sentence according to the tree position labels. Note that, when MSTparser outputs more than one trees for a sentence, we introduce a meta-root node to bundle the ones in a tree.</p></section><section number="4" title="Results and Discussions"><p>We use HMjVLSVM !as a sequence labeling model with features in Table 1, 2 and 3 for task A, B and C, respectively.   The attributes <i>value </i>in TIMEX3 is encoded as the relation with DCT-TIMEX3: {BEFORE, OVERLAP, AFTER, VAGUE}.In task A, only words in the current sentence with JOINT relation labels "TARGET/*" or "ANC/*"or "*/DES"<footnote anchor="2"/> were used. In task C, attributes in the TIMEX3 are annotated with the flag whether the TIMEX3 entity is the highest (namely the nearest to the root node) in the tree. Some adverbs and con­junctions in the succeeding sentence help to deter­mine the adjacent two relations. Thus, we introduce all words in the succeeding sentence for Task A and B. These features are determined by our preliminary experiments with the trial data .</p><footnote label="1">http://svmlight.joachims.org/svm_ struct.html</footnote><p>Table 4 is our results on the test data. Whereas, our system is average rank in task A and B, it is worst mark in task C. The features from dependency parsed trees are effective for task A and B. However, these are not for task C.</p><p>Now, we focus on what went wrong instead of what went right in our preliminary experiments in trial data. We tried point-wise methods with other _<u>Table 1 :</u><page local="4" global="248"/><u> Features for Task A</u>_</p><footnote label="2">'*' stands for wild cards.</footnote><p>all attributes in the target EVENT all attributes in the target TIMEX3 —the attributes <i>value </i>is encoded as the relation with <u>DCT-TIMEX3</u>_ all words in the current sentence with TIMEX3-based label (2) of tree position words in the current sentence with JOINT label (3) of tree position — only relation label with "TARGET/*" or "ANC/*"or label (1) of tree position from the EVENT to the all words in the succeeding sentence</p><doubt alpha="63.6" length="33" tooSmall="False" monospace="0.0">"*/DES" (* stands for wild cards)</doubt><doubt alpha="71.4" length="7" tooSmall="False" monospace="0.0">TIMEX3_</doubt><p>_<u>Table 2: Features for Task B</u>_</p><p>all attributes in the target EVENT all attributes in the target TIMEX3 of in the current sen­tence with EVENT-based label (1) of tree position all attributes in the target TIMEX3 of in the preceding and succeeding sentence all words in the current sentence with EVENT-based la­bel (1) of tree position all words in the succeeding sentence</p><p>_<u>Table 3 : Features for Task C</u>_</p><p>all attributes in the target two EVENTs (EVENT-1 and all attributes in the TIMEX3 in the sentence including EVENT-1 with the label (1) of tree position to EVENTall attributes in the TIMEX3 in the sentence including EVENT-2 with the label (1) of tree position to EVENTall words in the sentence including EVENT-1 with the label (1) of tree position to EVENT-1 all words in the sentence including EVENT-2 with the label (1) of tree position to EVENT-2</p><doubt alpha="55.6" length="9" tooSmall="False" monospace="0.0">EVENT-2)_</doubt><doubt alpha="0.0" length="2" tooSmall="False" monospace="0.0">1_</doubt><doubt alpha="0.0" length="2" tooSmall="False" monospace="0.0">2_</doubt><p>machine learners such as maximum entropy and multi-class support vector machines. However, se­quence labeling method with HMjVLSVM outper­formed other point-wise methods in the trial data.</p><p>We have dependency parsed trees of the sen­tences. Naturally, it would be effective to intro­duce point-wise tree-based classifiers such as Tree Kernels in SVM (Collins and Duffy, 2002; Vish-wanathan and Smola, 2002) and boosting for clas­sification of trees (Kudo and Matsumoto, 2004). We tried a boosting learner <footnote anchor="3"/>which enables us to perform subtree feature selection for the tasks. However, the boosting learner selected only one-node subtrees as useful features. Thus, we perform simple vector-based feature engineering on HMjVLSVM.</p><footnote label="3">http://chasen.org/~taku/software/bact/</footnote><table caption="Table 4: Results"></table><p>We believe that it is necessary for solving task C to incorporate knowledge of verb-verb relation. We also tried to use features in verb ontology such as VERBOCEAN (Chklovsky and Pantel, 2004) which is used in (Mani et al., 2006). It did not improved performance in our preliminary experiments with trial data.</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>Task</p></td><td class="cell"><p>P       R F</p></td><td class="cell"><p>Rank</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p>Task A (strict) Task A (relaxed)</p></td><td class="cell"><p>0.61    0.61 0.61 0.63    0.63 0.63</p></td><td class="cell"><p>2/6 2/6</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p>Task B (strict) Task B (relaxed)</p></td><td class="cell"><p>0.75    0.75 0.75 0.76    0.76 0.76</p></td><td class="cell"><p>2/6 2/6</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p>Task C (strict) Task C (relaxed)</p></td><td class="cell"><p>0.49    0.49 0.49 0.56    0.56 0.56</p></td><td class="cell"><p>5/6 6/6</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></section><references><p>Y. Altun, I. Tsochantaridis, and T. Hofmann. 2003. Hid­den markov support vector machines. In <i>Proc. of ICML-2003.</i></p><p>T. Chklovsky and P. Pantel. 2004. Verbocean: Mining the web for fine-grained semantiv verb relations. In</p><p><i>Proc. ofEMNLP-2004.</i></p><p>M. Collins and N. Duffy. 2002. New ranking algorithms for parsing and tagging: Kernels over discrete struc­tures, and the voted perceptron. In <i>Proc. ofACL-2002.</i></p><p>T. Kudo and Y. Matsumoto. 2004. A boosting algorithm for classification of semi-structured text. In <i>Proc. of</i></p><p><i>EMNLP-2004.</i></p><p>I. Mani, M. Verhagen, B. Wellner, C. M. Lee, and J. Pustejovsky. 2006. Machine learning of temporal relations. In <i>Proc. ofACL-2006.</i></p><p>M. Marcus, B. Santorini, and M. Marcinkiewicz. 1993. Building a large annotated corpus ofEnglish: the Penn Treebank. 19(2):313-330.</p><p>R. McDonald and F. Pereira. 2006. Online learning of approximate dependency parsing algorithms. In <i>Proc.</i></p><p><i>ofEACL-2006.</i></p><p>M. Verhagen, R. Gaizauskas, F. Schilder, M. Hepple, and J. Pustejovsky. 2007. Semeval-2007 task 15: Tempeval temporal relation identification. In <i>Proc. of SemEval-2007.</i></p><p>S. V. N. Vishwanathan and A. J. Smola. 2002. Fast ker­nels on strings and trees. In <i>Proc. ofNIPS-2002.</i></p></references></body></article>