<?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="325"/><title>KUL: Recognition and Normalization of Temporal Expressions</title><pubinfo>Proceedings of the 5th International Workshop on Semantic Evaluation, ACL 2010,pages 325-328, Uppsala, Sweden, 15-16 July 2010. ©2010 Association for Computational Linguistics</pubinfo><author surname="Kolomiyets" givenname="Oleksandr"><org  name="Katholieke Universiteit Leuven" country="Belgium" city="Leuven"/></author><author surname="Moens" givenname="Marie-Francine"><org  name="Katholieke Universiteit Leuven" country="Belgium" city="Leuven"/></author></firstpageheader><frontmatter><p><b>KUL: Recognition and Normalization of Temporal Expressions</b></p><p><b>Oleksandr Kolomiyets, Marie-Francine Moens</b></p><p>Department of Computer Science Katholieke Universiteit Leuven {oleksandr.kolomiyets,  sien.moens}@cs.kuleuven.be</p></frontmatter><abstract>In this paper we describe a system for the recognition and normalization of temporal expressions (Task 13: TempEval-2, Task A). The recognition task is approached as a classification problem of sentence con­stituents and the normalization is imple­mented in a rule-based manner. One of the system features is extending positive an­notations in the corpus by semantically similar words automatically obtained from a large unannotated textual corpus. The best results obtained by the system are 0.85 and 0.84 for precision and recall re­spectively for recognition of temporal ex­pressions; the accuracy values of 0.91 and 0.55 were obtained for the feature values TYPE and VAL respectively. </abstract></header><body><section number="1" title="Introduction"><p>Recognition of temporal expressions<footnote anchor="1"/> is a task of proper identification of phrases with temporal semantics in running text. After several evalua­tion campaigns targeted at temporal processing of text, such as MUC, ACE TERN and TempEv-al-1 (Verhagen et al., 2007), the recognition and normalization task has been again newly reintro-duced in TempEval-2 (Pustejovsky &amp; Verhagen, 2009). The task is defined as follows: determine the extent of the time expressions; in addition, determine the value of the features TYPE for the type of the temporal expression and its temporal value VAL. In this paper we describe the KUL system that has participated in this task.</p><footnote label="1">Temporal expressions are sometimes referenced as time expressions and timexes.</footnote><p>Architecturally, the system employs a pipe­lined information processing chain and imple­ments a number of machine learning classifiers for extracting the necessary information for the temporal value estimation. The normalization step employs a number of hand-crafted vocabula­ries for tagging single elements of a temporal expression and a rule-based system for estimat­ing the temporal value. The performance of the system obtained the values of 0.85 and 0.84 for precision and recall respectively for the recogni­tion of temporal expressions. The accuracy for the type and value is 0.91 and 0.55 respectively.</p><p>The remainder of the paper is organized as follows: Section 2 reports on the architecture of the system with single modules and describes theirs functions. Section 3 presents the results and error analysis; the conclusions are provided in Section 4.</p></section><section number="2" title="System Architecture"><p>The system is implemented in Java and follows a pipelined method for information processing. Regarding the problems it solves, it can be split in two sub-systems: recognition and normaliza­tion.</p><subsection number="2.1" title="Recognition of Temporal Expressions"><p>This sub-system is employed for finding tempor­al expressions in the text. It takes a sentence as input and looks for temporal expressions in it.</p><p><b>Pre-processing: </b>At this step the input text un­dergoes syntactic analysis. Sentence detection, tokenization, part-of-speech tagging and parsing are applied<footnote anchor="2"/>.</p><p><b>Candidate selection: </b>Since only certain lexi­cal categories can be temporal expressions and they are defined in the TIDES standard (Ferro et al., 2003), in our implementation we consider the following chunk-phrases as candidates for tem­poral expressions:<page local="2" global="326"/> nouns <i>(week, day), </i>proper names <i>(Tuesday, May), </i>noun phrases <i>(last Tues­day), </i>adjectives <i>(current), </i>adjective phrases <i>(then current), </i>adverbs <i>(currently), </i>adverbial phrases (a <i>year ago), </i>and numbers <i>(2000). </i>As input it takes the sentences with provided syntactic in­formation and marks phrases in the parse tree belonging to the above types for temporal ex­pressions.</p><footnote label="2">For preprocessing we use the OpenNLP package ( http:// opennlp. sourceforge.net ).</footnote><p><b>Annotation alignment: </b>If the system is used for training classifiers, all the candidates in a sentence are examined against the available an­notations. The candidates, whose parse and anno­tation extents aligned, are taken as positive ex­amples and the rest is considered as negative.</p><p><b>Feature Design: </b>To produce a feature-vector we use most valuable features extracted for phrase-candidate. After a number of experiments the following features were selected:</p><p>• Last token in the phrase, most probable token to be a temporal trigger;</p><p>• Lemma of the last phrasal token;</p><p>• Part-of-speech of the last phrasal token;</p><p>• Character pattern of the last phrasal to­ken as introduced in (Ahn et al., 2007);</p><p>• Neighbor POS's. The concatenated part-of-speech tags of the last phrasal token and its preceding token;</p><p>• Character pattern of the entire phrase;</p><p>• Phrase surface. A concatenated string of sub-parse types for the phrase;</p><p>• A Boolean feature indicating nested complex phrasal parses, such as noun verb, adverbial, adjective or preposition­al phrase;</p><p>• Depth of the phrase. The number of the nested sub-parses to the deepest pre-terminal sub-parse.</p><p>All the features are considered as Boolean.</p><p><b>Classification: </b>Once the classifiers are trained they can be used for recognition of temporal ex­pressions on test sentences. A preprocessed sen­tence is taken as input and starting from its parse-tree root the candidate-phrases are classi­fied. The most probable class will be assigned to the candidate under consideration. Once the phrase is classified as temporal expression no further classification of nested phrases is per­formed, since no embedded timexes are allowed in the corpus. After a series of experiments with different machine learning techniques on the training data the maximum entropy classifier was chosen.</p><p><b>Extending positive instances: </b>Sparseness of annotated corpora is the biggest challenge for any supervised machine learning technique. To overcome this problem we hypothesize that knowledge of semantic similar words could be found by associating words that do not occur in the training set to similar words that did occur in the training set. Furthermore, we would like to learn these similarities automatically in order to be as much as possible independent of know­ledge sources that might not be available for all languages or domains. For example, there is in TimeBank a temporal expression <i>"last summer" </i>with the temporal trigger <i>summer, </i>but there is no annotation of temporal expressions built around the temporal trigger <i>winter, </i>and this means that no temporal expression with the trigger <i>winter </i>can be recognized. Something similar usually happens to any annotated corpus and we want to find a way how to find other temporal expres­sions outside the available data, which can be used for training. On the other hand, we want to avoid a naïve selection of words as, for example, from a gazetteer with temporal triggers, which may contradict with grammatical rules and the lexical context of a timex in text, e.g.:</p><p>on <i>Tuesday </i>said....</p><p>But grammatically wrong by naïve replacement from a gazetteer:</p><p>... on <b><i>week </i></b>said*... ... on <b><i>day </i></b>said*... ... on <b><i>month </i></b>said* ...</p><p>In order to find these words, which are legiti­mate at a certain position in a certain context we use the latent word language model (LWLM) (Deschacht &amp; Moens, 2009) with a Hidden Mar­kov Model approach for estimating the latent word parameters.</p><p>Complementary, we use WordNet (Miller, 1995) as a source that can provide a most com­plete set of words similar to the given one. One should note that the use of WordNet is not straight-forward. Due to the polysemy, the word sense disambiguation (WSD) problem has to be solved. Our system uses latent words obtained by the LWLM and chooses the synset with the highest overlap between WordNet synonyms and coordinate terms, and the latent words.<page local="3" global="327"/> The over­lap value is calculated as the sum of LWLM probabilities for matching words.</p><p>Having these two sets of synonyms and after a series of preliminary tests we found the setting, at which the system produces the highest results and submitted several runs with different strate­gies:</p><p>• Baseline (no expansion) (KUL Run 1)</p><p>• 3 LWLM words with highest probabili­ties (KUL Run 2)</p><p>• 3 WordNet coordinate terms; WSD is solved by means of LWLM<footnote anchor="3"/> (KUL Run</p><doubt alpha="0.0" length="2" tooSmall="False" monospace="0.0">3)</doubt><p>For each available annotation in the corpus a positive instance is generated. After that, the to­ken at the most probable position for a temporal trigger is replaced by a synonym from the syn­onym set found to the available token.</p></subsection><subsection number="2.2" title="Normalization of Temporal Expressions"><p>Normalization of temporal expressions is a process of estimating standardized temporal val­ues and types. For example, the temporal expres­sion <i>"summer 1990" </i>has to be resolved to its value of 1990-SU and the type of DATE. In contrast, for the expression <i>"lastyear" </i>the value cannot be estimated directly, rather it gets a mod­ified value of another time expression.</p><p>Due to a large variance of expressions denot­ing the same date and vagueness in language, rule-based systems have been proven to perform better than machine-learning ones for the norma­lization task. The current implementation follows a rule-based approach and takes a pre-processed document with recognized temporal expressions (as it is described in Section 2.1) and estimates a standardized ISO-based date/time value. In the following sections we provide implementation details of the system.</p><p>Before the temporal value is estimated, we employ a classifier, which uses the same feature sets and classify the temporal expression among type classes DATE, TIME, DURATION and SET.</p><p><b>Labeling: </b>Labeling text is a process of provid­ing tags to tokens of chunk-phrases from a defined set of tags. We carefully examined availa­ble annotated temporal expressions and annota­tion standards to determine categories of words participating in temporal expressions. The fol­lowing set of categories with labels based on se­mantics of temporally relevant information and simple syntax was defined: ordinal numbers <i>(first, 30th </i>etc.), cardinal numbers <i>(one, two, 10 </i>etc.), month names <i>(Jan., January </i>etc.), week day names (Mo., <i>Monday </i>etc.), season names <i>(summer, winter </i>etc.), parts of day <i>(morning, afternoon </i>etc.), temporal directions (ago, <i>later, earlier </i>etc.), quantifiers <i>(several, few </i>etc.), mod­ifiers <i>(recent, last </i>etc.), approximators <i>(almost, nearly </i>etc.), temporal co-references <i>(time, period </i>etc.), fixed single token timexes <i>(tomorrow, to­day </i>etc.), holidays <i>(Christmas, Easter </i>etc.) and temporal units <i>(days, months, years </i>etc.). Also fine-grained categories are introduced: day num­ber, month number and year number. For each category we manually construct a vocabulary, in which each entry specifies a value of a temporal field or a final date/time value, or a method with parameters to apply.</p><footnote label="3">Preliminary experiments, when the most common sense in WordNet is chosen for increasing the number of positive examples, showed a low performance level and thus has not been proposed for evaluations.</footnote><p>As input, the normalization takes a recognized temporal expression and its properties, such as the temporal type and the discourse type<footnote anchor="4"/>. During labeling each token in a temporal expression is tagged with one or multiple labels corresponding to the categories defined above. For each of the categories a custom detector is implemented. The detector declares the method to run and the ex­pected type of the result. The rules that imple­ment the logics for the detector are inherited from an abstract class for this specific detector, so that if a new rule needs to be implemented its realization is limited to the development of one class, all the rest the detector does automatically. Besides, the order, in which detectors have to be run, can be specified (as for example, in case of fine-grained detectors). As output, the module provides labels of the categories to the tokens in the temporal expression. If there is no entry in the vocabulary for a token, its part-of-speech tag is used as the label.</p><p><b>Value estimation: </b>Value estimation is implemented in the way of aggregating the values defined for entries in the vocabulary and/or executing instructions or methods specified. Also a set of predefined resolution rules is provided and can be extended with new implementations of resolution strategies.<page local="4" global="328"/></p><footnote label="4">Since in TempEval-2 the reference to the timex with re­spect to which the value estimated is given, the normaliza­tion module considers all timexes as deictic.</footnote><p>For resolution of complex relative temporal expressions, the value for which cannot be esti­mated directly, we need to rely on additional in­formation found at the recognition step. This in­cludes the semantic type of the timex, discourse type and contextual temporal information (speech or document creation time, or previously mentioned timexes). Let's consider the following temporal expression as an example: <i>10 days ago. </i>In this example the temporal expression receives a modified value of another timex, namely the value of the document creation time. The tem­poral expression is recognized and classified as a date (SEM TYPE : DATE), which refers to another timex (DISCOURSE TYPE: DEIC­TIC). It takes the value of the referenced timex and modifies it with respect to the number <i>(10), </i>magnitude <i>(days) </i>and temporal direction <i>(ago). </i>Thus, the final value is calculated by subtracting a number of days for the value of the referenced timex.</p></subsection></section><section number="3" title="Results and Error Analysis"><p>In the Table 1 the results of the best-performing runs are presented.</p><p>As we can see the best results were obtained by extending available annotations with maxi­mum 3 additional instances, which are extracted as coordinate terms in WordNet, whereas the WSD problem was solved as the greatest overlap between coordinate terms and latent words ob­tained by the LWLM.</p><p>Most of the errors at the recognition step were caused by misaligned parses and annotations.</p><p>For normalization we acknowledge the signi­ficance of estimating a proper temporal value with a correct link to the temporal expression with its value. In the TempEval-2 training data the links to the temporal expressions indicating how the value is calculated were not provided, and thus, the use of machine learning tools for training and automatic disambiguation was not possible. We choose a fixed strategy and all rela­tive temporal expressions were resolved with respect to the document creation time, which caused errors with wrong temporal values and a low performance level.</p></section><section number="4" title="Conclusions"><p>For TempEval-2 we proposed a system for the recognition and normalization of temporal ex­pressions. Multiple runs were submitted, among which the best results were obtained with auto­matically expanded positive instances by words derived as coordinate terms from WordNet for which the proper sense was found as the greatest overlap between coordinate terms and latent words found by the LWLM.</p></section><section title="Acknowledgements"><p>This work has been funded by the Flemish gov­ernment as a part of the project AMASS++ (Grant: IWT-60051) and by Space Applications Services NV as part of the ITEA2 project LIN-</p><p>DO (ITEA2-06011, IWT-70043).</p><table caption="Table 1. Results of different runs of the system." 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></tr><tr class="row"><td class="cell"></td><td class="cell"><p>Run</p></td><td class="cell"><p>Recognition</p></td><td class="cell"><p>Normalization</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p></p></td><td class="cell"><p><i>P</i></p></td><td class="cell"><p><i>R</i></p></td><td class="cell"><p><i>F1</i></p></td><td class="cell"><p>TYPE Acc.</p></td><td class="cell"><p>VAL Acc.</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p>1</p></td><td class="cell"><p>0.78</p></td><td class="cell"><p>0.82</p></td><td class="cell"><p>0.8</p></td><td class="cell"><p>0.91</p></td><td class="cell"><p>0.55</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p>2</p></td><td class="cell"><p>0.75</p></td><td class="cell"><p>0.85</p></td><td class="cell"><p>0.797</p></td><td class="cell"><p>0.91</p></td><td class="cell"><p>0.51</p></td><td class="cell"></td></tr><tr class="row"><td class="cell"></td><td class="cell"><p>3</p></td><td class="cell"><p>0.85</p></td><td class="cell"><p>0.84</p></td><td class="cell"><p>0.845</p></td><td class="cell"><p>0.91</p></td><td class="cell"><p>0.55</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></tr></table></section><references><p>Ahn, D., van Rantwijk, J., and de Rijke, M. 2007. A Cascaded Machine Learning Approach to Interpret­ing Temporal Expressions. In <i>Proceedings of NAACL-HLT 2007.</i></p><p>Deschacht, K., and Moens M.-F. 2009. Using the La­tent Words Language Model for Semi-Supervised Semantic Role Labeling. In <i>Proceedings of the Conference on Empirical Methods in Natural Lan­guage Processing.</i></p><doubt alpha="60.0" length="50" tooSmall="False" monospace="0.0">Ferro, L., Gerber, L., Mani, I., Sundheim, B., and</doubt><doubt alpha="59.1" length="44" tooSmall="False" monospace="0.0">Wilson, G. 2003. TIDES 2003 Standard for the</doubt><p>Annotation of Temporal Expressions.</p><p>Miller, G. A. 1995. WordNet: A Lexical Database for English. <i>Communications of the ACM, </i>38(11): 39­41.</p><p>Pustejovsky, J. and Verhagen, M. 2009. SemEval-2010 Task 13: Evaluating Events, Time Expres­sions, and Temporal Relations (TempEval-2). In <i>Proceedings of the Workshop on Semantic Evalua­tions: Recent Achievements and Future Directions.</i></p><p>Verhagen, M., Gaizauskas, R., Schilder, F., Hepple, 15: Tempeval Temporal Relation Identification. In <i>SemEval-2007: 4th International Workshop on Semantic Evaluations.</i></p><doubt alpha="57.4" length="47" tooSmall="False" monospace="0.0">M., and Pustejovsky, J. 2007. Semeval-2007 Task</doubt></references></body></article>