File size: 45,308 Bytes
6fa4bc9 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 | {
"paper_id": "S13-2003",
"header": {
"generated_with": "S2ORC 1.0.0",
"date_generated": "2023-01-19T15:42:56.068103Z"
},
"title": "HeidelTime: Tuning English and Developing Spanish Resources for TempEval-3",
"authors": [
{
"first": "Jannik",
"middle": [],
"last": "Str\u00f6tgen",
"suffix": "",
"affiliation": {
"laboratory": "",
"institution": "Heidelberg University",
"location": {
"addrLine": "Im Neuenheimer Feld 348",
"postCode": "69120",
"settlement": "Heidelberg",
"country": "Germany"
}
},
"email": ""
},
{
"first": "Julian",
"middle": [],
"last": "Zell",
"suffix": "",
"affiliation": {
"laboratory": "",
"institution": "Heidelberg University",
"location": {
"addrLine": "Im Neuenheimer Feld 348",
"postCode": "69120",
"settlement": "Heidelberg",
"country": "Germany"
}
},
"email": "j.zell@stud.uni-heidelberg.de"
},
{
"first": "Michael",
"middle": [],
"last": "Gertz",
"suffix": "",
"affiliation": {
"laboratory": "",
"institution": "Heidelberg University",
"location": {
"addrLine": "Im Neuenheimer Feld 348",
"postCode": "69120",
"settlement": "Heidelberg",
"country": "Germany"
}
},
"email": "gertz@uni-hd.de"
}
],
"year": "",
"venue": null,
"identifiers": {},
"abstract": "In this paper, we describe our participation in the TempEval-3 challenge. With our multilingual temporal tagger HeidelTime, we addressed task A, the extraction and normalization of temporal expressions for English and Spanish. Exploiting HeidelTime's strict separation between source code and languagedependent parts, we tuned HeidelTime's existing English resources and developed new Spanish resources. For both languages, we achieved the best results among all participants for task A, the combination of extraction and normalization. Both the improved English and the new Spanish resources are publicly available with HeidelTime.",
"pdf_parse": {
"paper_id": "S13-2003",
"_pdf_hash": "",
"abstract": [
{
"text": "In this paper, we describe our participation in the TempEval-3 challenge. With our multilingual temporal tagger HeidelTime, we addressed task A, the extraction and normalization of temporal expressions for English and Spanish. Exploiting HeidelTime's strict separation between source code and languagedependent parts, we tuned HeidelTime's existing English resources and developed new Spanish resources. For both languages, we achieved the best results among all participants for task A, the combination of extraction and normalization. Both the improved English and the new Spanish resources are publicly available with HeidelTime.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Abstract",
"sec_num": null
}
],
"body_text": [
{
"text": "The task of temporal annotation, which is addressed in the TempEval-3 challenge, consists of three subtasks: (A) the extraction and normalization of temporal expressions, (B) event extraction, and (C) the annotation of temporal relations . This makes sub-task A, i.e., temporal tagging, a prerequisite for the full task of temporal annotating documents. In addition, temporal tagging is important for many further natural language processing and understanding tasks, and can also be exploited for search and exploration scenarios in information retrieval (Alonso et al., 2011) .",
"cite_spans": [
{
"start": 555,
"end": 576,
"text": "(Alonso et al., 2011)",
"ref_id": "BIBREF0"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "Introduction",
"sec_num": "1"
},
{
"text": "In the context of the TempEval-2 challenge (Verhagen et al., 2010), we developed our temporal tagger HeidelTime (Str\u00f6tgen and Gertz, 2010) , which achieved the best results for the extraction and nor-malization of temporal expressions for English documents. For our work on multilingual information retrieval (e.g., ), we extended HeidelTime with a focus on supporting the simple integration of further languages (Str\u00f6tgen and Gertz, 2012a) . For TempEval-3, we now tuned Heidel-Time's English resources and developed new Spanish resources to address both languages that are part of TempEval-3. As the evaluation results demonstrate, HeidelTime outperforms the systems of all other participants for the full task of temporal tagging by achieving high quality results for the extraction and normalization for English and Spanish.",
"cite_spans": [
{
"start": 112,
"end": 138,
"text": "(Str\u00f6tgen and Gertz, 2010)",
"ref_id": "BIBREF4"
},
{
"start": 413,
"end": 440,
"text": "(Str\u00f6tgen and Gertz, 2012a)",
"ref_id": "BIBREF5"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "Introduction",
"sec_num": "1"
},
{
"text": "The remainder of the paper is structured as follows: We explain HeidelTime's system architecture in Section 2. Section 3 covers the tuning of Heidel-Time's English and the development of the Spanish resources. Finally, we discuss the evaluation results in Section 4, and conclude the paper in Section 5.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Introduction",
"sec_num": "1"
},
{
"text": "HeidelTime is a multilingual, cross-domain temporal tagger. So far, it can process English, German, and Dutch text. In previous work, we analyzed domain-dependent challenges and demonstrated that domain-sensitive strategies for normalizing temporal expressions result in significant normalization improvements when switching between news-and narrative-style documents (Str\u00f6tgen and Gertz, 2012b) . Although TempEval-3 only addresses news documents, the tuned English and new Spanish resources can be used to process news and also narrative-style documents such as Wikipedia articles with high extraction and normalization quality.",
"cite_spans": [
{
"start": 368,
"end": 395,
"text": "(Str\u00f6tgen and Gertz, 2012b)",
"ref_id": "BIBREF6"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "HeidelTime",
"sec_num": "2"
},
{
"text": "Architecture of HeidelTime. HeidelTime is a rule-based system with a strict separation between source code and language-dependent resources. While the strategies for processing different domains are part of the source code, resources consist of files for (i) patterns, (ii) normalizations, and (iii) rules. They are read by HeidelTime's resource interpreter and thus have to be developed based on HeidelTime's well-defined rule syntax.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "HeidelTime",
"sec_num": "2"
},
{
"text": "The pattern files contain words and phrases, which are typically used to express temporal expressions, e.g., names of months. The normalization files contain normalization information about the patterns, e.g., the value of a specific month's name. Finally, the rule files contain rules for date, time, duration, and set expressions.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "HeidelTime",
"sec_num": "2"
},
{
"text": "All rules have an extraction part and a normalization part. The extraction part, in which the pattern resources can be used for generalization, defines the expressions that have to be matched in a document. The normalization part normalizes the context-independent content of the expression using the normalization resources. While explicit temporal expressions (e.g., May 1st, 2013) can directly be fully normalized, underspecified (November) and relative (today, two weeks ago) expressions can only be normalized in an underspecified manner. The full normalization depends on the domain of the document that is to be processed and the context of the expression. For this, HeidelTime applies domainsensitive strategies to normalize such expressions during its disambiguation phase, which is called after the extraction and the normalization phases.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "HeidelTime",
"sec_num": "2"
},
{
"text": "The TempEval-3 data is from the news domain. Here, HeidelTime usually uses the document creation time as reference time. The temporal relation to it is identified based on the tense in the sentence. 1",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "HeidelTime",
"sec_num": "2"
},
{
"text": "Preprocessing. HeidelTime requires sentence, token, and part-of-speech information. For this, the TreeTagger (Schmid, 1994) is used. Since there is a Spanish model for the TreeTagger, adding Spanish preprocessing capabilities to HeidelTime was fairly easy. A wrapper for the TreeTagger is also part of the UIMA HeidelTime kit described next.",
"cite_spans": [
{
"start": 109,
"end": 123,
"text": "(Schmid, 1994)",
"ref_id": "BIBREF3"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "HeidelTime",
"sec_num": "2"
},
{
"text": "UIMA HeidelTime kit. For processing Temp-Eval-3 data, we used the UIMA version of Heidel-Time, developed a collection reader and a CAS consumer to read and write TempEval-3 input and output data, and added both components to our UIMA HeidelTime kit. This makes HeidelTime's evaluation results reproducible on the training and test sets.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "HeidelTime",
"sec_num": "2"
},
{
"text": "In TempEval-3, we participated with one Spanish and three English runs: For Spanish, we used our newly developed resources. For English, we used (i) HeidelTime 1.2, which was released in May 2012, (ii) a version containing several bug fixes and improvements, which were implemented independently from TempEval-3, and (iii) HeidelTime with its new English resources tuned for TempEval-3.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "HeidelTime for TempEval-3",
"sec_num": "3"
},
{
"text": "In general, our goal when developing HeidelTime resources is to achieve high quality normalization results. Thus, we only want to extract temporal expressions which can be normalized correctly with high probability -an issue, which will be further looked at in the discussion in the evaluation section. Before that, we next describe language-independent adaptations to HeidelTime. Then, we present the tuning of the English resources (Section 3.2) and the development of the Spanish resources (Section 3.3).",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "HeidelTime for TempEval-3",
"sec_num": "3"
},
{
"text": "We performed the following language-independent changes to HeidelTime:",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "General HeidelTime Adaptations",
"sec_num": "3.1"
},
{
"text": "(i) Weekday normalization: In news-style documents, extracted weekdays that are equal to the weekday of the document creation time (dct) are now normalized to the date of the dct independent of the tense in the sentence.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "General HeidelTime Adaptations",
"sec_num": "3.1"
},
{
"text": "(ii) Century/decade normalization: So far, decade and century expressions were not correctly normalized by HeidelTime according to TimeML, e.g., \"199X\" instead of \"199\" for \"the 1990s\".",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "General HeidelTime Adaptations",
"sec_num": "3.1"
},
{
"text": "The first change is based on the intuitive assumption that information in news-style documents is temporally focused around the dct. In addition, this assumption is supported by the English and the Spanish training data. The second change is related to the annotation standard. Both changes can thus be generalized in a language-independent manner.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "General HeidelTime Adaptations",
"sec_num": "3.1"
},
{
"text": "Three training corpora were provided by the organizers: the Aquaint and TimeBank gold standard corpora, and a large corpus referred to as silver standard, which was created by merging results of three tools . After a brief analysis, we decided not to use the silver standard due to the rather low annotation quality. Motivated by observations in the gold standard corpora, we performed the following English-specific modifications in addition to the general adaptations described above:",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Tuning HeidelTime's English Resources",
"sec_num": "3.2"
},
{
"text": "(i) REF-value expressions: expressions normalized to past, present, or future are not consistently annotated in the training data. Since such expressions are rather less valuable for further tasks and to avoid false positives, we removed some of those patterns from the resources.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Tuning HeidelTime's English Resources",
"sec_num": "3.2"
},
{
"text": "(ii) Ambiguous expressions: We added negative rules for expressions such as may, march, and fall to filter them out if they do not refer to a date.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Tuning HeidelTime's English Resources",
"sec_num": "3.2"
},
{
"text": "(iii) Article/modifier: We allowed some more combinations of articles and modifiers.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Tuning HeidelTime's English Resources",
"sec_num": "3.2"
},
{
"text": "Note that HeidelTime was already a state-of-theart tool for English temporal tagging so that the changes are rather minor.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Tuning HeidelTime's English Resources",
"sec_num": "3.2"
},
{
"text": "In this section, we explain the resource development process for Spanish. Then, we detail languagespecific challenges we faced during this process.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Developing Spanish Resources",
"sec_num": "3.3"
},
{
"text": "Resource Development Process. So far, there were no HeidelTime resources for Spanish, and we thus started the development from scratch. (i) Preprocessing: As mentioned in Section 2, we use the TreeTagger with its Spanish module for sentence, token, and part-of-speech annotation.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Developing Spanish Resources",
"sec_num": "3.3"
},
{
"text": "(ii) Translation of pattern files: Starting with Hei-delTime's English pattern resources, we developed the Spanish pattern resources. The goal was that all patterns that are frequently used to express temporal expressions are included in the resources. Note that it is not important that the patterns are context independent. The context in which a pattern should occur can be defined within the rules.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Developing Spanish Resources",
"sec_num": "3.3"
},
{
"text": "(iii) Translation of normalization files: Similar to the patterns, we translated the English normalization files and adapted them to the new Spanish patterns.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Developing Spanish Resources",
"sec_num": "3.3"
},
{
"text": "(iv) Rule Development: Based on the English rules for dates, times, durations, and sets, we developed similar Spanish rules. Using the Spanish training corpus to check for partially matching patterns, false positives, false negatives, and incorrect normalizations, we then iteratively adapted the rules, but also the pattern and normalization resources.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Developing Spanish Resources",
"sec_num": "3.3"
},
{
"text": "Challenges. Spanish as a Romance language is rich in inflection. Nouns, adjectives, and determiners are inflected with respect to number and gender. During the development of the pattern and normalization resources, this had to be taken into account.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Developing Spanish Resources",
"sec_num": "3.3"
},
{
"text": "As for nouns, there are many inflection forms of verbs in Spanish, e.g., to represent tense. While verbs are usually not part of temporal expressions, the inflection of verbs has to be considered for the normalization of ambiguous expressions such as el lunes (Monday) or junio (June). As mentioned above, in news-style documents, HeidelTime uses the tense of the sentence to determine the relation to the reference time, i.e., to decide whether the expression refers to a previous or upcoming date.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Developing Spanish Resources",
"sec_num": "3.3"
},
{
"text": "The tense is determined using part-of-speech information, and, if necessary, pattern information of words with specific part-of-speech tags. For each language, this information is defined in the pattern resources. Unfortunately, the Spanish tag-set of the TreeTagger module does not contain tags covering tense information, e.g., all finite lexical verbs are tagged as VLfin. Thus, we created regular expression patterns to match typical inflection patterns representing tense information and check words tagged as verbs by the tagger for these patterns.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Developing Spanish Resources",
"sec_num": "3.3"
},
{
"text": "However, due to the ambiguity of the Spanish inflection, we can only add patterns to detect future tense. If no tense is identified, the year is set to the year of the reference time. As detailed in the discussion of the evaluation results described in Section 4, identifying the correct relation to the reference time is a frequent source of normalization errors.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Developing Spanish Resources",
"sec_num": "3.3"
},
{
"text": "Measures. For the extraction task, precision (P), recall (R), and f 1 -score (F1) are used for strict and relaxed matching. The value F1 and type F1 measures combine relaxed matching with correct normalization. Systems are ranked by value F1 (value). Results on Training Data. Table 1 shows the results on the Aquaint (a), TimeBank (b), and Spanish training corpora (c). On both English corpora, Hei-delTime's TempEval-3 tuned version outperforms the other two versions. The big differences between the two English corpora are rather due to the better annotation quality of TimeBank than due to different challenges in the documents of the two corpora.",
"cite_spans": [],
"ref_spans": [
{
"start": 277,
"end": 284,
"text": "Table 1",
"ref_id": "TABREF1"
}
],
"eq_spans": [],
"section": "Evaluation Results",
"sec_num": "4"
},
{
"text": "TempEval-3 Evaluation. The evaluation results on the test data are presented in Table 2 . For English, HeidelTime's TempEval-3 tuned version achieves the best results, and all three HeidelTime versions outperform the systems of the eight other participating teams with a total number of 21 submissions (task A ranking measure value F1). For comparison, the results of the next best system (NavyTime) is listed in Table 2 (a). For Spanish, we highly outperform the other two systems, as shown in Table 2 (b).",
"cite_spans": [],
"ref_spans": [
{
"start": 80,
"end": 87,
"text": "Table 2",
"ref_id": "TABREF3"
},
{
"start": 413,
"end": 420,
"text": "Table 2",
"ref_id": "TABREF3"
},
{
"start": 495,
"end": 502,
"text": "Table 2",
"ref_id": "TABREF3"
}
],
"eq_spans": [],
"section": "Evaluation Results",
"sec_num": "4"
},
{
"text": "Discussion. In order to be able to interpret Hei-delTime's results on the training and test data, we performed an error analysis (TimeBank and Spanish training corpus). The most important findings are: (i) For a rule-based system, HeidelTime's recall is relatively low (many false negatives; FN). However, note that several FN are intentional. 55% and 29% of 117 and 149 FN in the English and Spanish training corpora are due to imprecise expressions (some time; the latest period). These are difficult to normalize correctly, e.g., some time can refer to seconds or years. To guarantee high quality normalization, we do not extract expressions that cannot be normalized correctly with high probability.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Evaluation Results",
"sec_num": "4"
},
{
"text": "(ii) There is a trade-off between precision and recall due to expressions referring to past, present, or future (X REF). These are annotated either only in some contexts or inconsistently throughout the train- ing data, and thus result in FN (21%/en; 34%/es) and false positives (43% of 98 FP in English training and 43%/es of 35 FP in Spanish training corpora). (iii) The main sources for incorrect value normalization of underspecified expressions (Feb. 1; Monday) are wrongly detected reference times or relations to them (e.g., due to wrong tense identification), annotation errors in the corpora (e.g., last week annotated as WXX instead of the week it is referring to), granularity errors (e.g., a year ago can refer to a day, month, quarter, or year), and ambiguities (e.g., the year can be a duration or a specific year).",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Evaluation Results",
"sec_num": "4"
},
{
"text": "(iv) Some expressions in the Spanish test set were extracted and normalized correctly although no similar expressions exist in the Spanish training data. Here, the Spanish resources highly benefited from the high quality English resources as starting point of the development process, and from HeidelTime's language-independent normalization strategies.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Evaluation Results",
"sec_num": "4"
},
{
"text": "(v) A reoccurring error in the English test set is that HeidelTime matches and normalizes expressions such as two days earlier while only two days should be annotated according to TimeML. This results in a relaxed match with false type and value.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Evaluation Results",
"sec_num": "4"
},
{
"text": "In this paper, we presented HeidelTime's results in the TempEval-3 temporal tagging task. For both languages, English and Spanish, we achieved the best results of all participants (value F1). We showed that adding a new language to HeidelTime can result in high quality temporal tagging of the new language.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Conclusions & Ongoing Work",
"sec_num": "5"
},
{
"text": "Currently, we are working on improving the Spanish tense detection to better normalize underspecified temporal expressions. Furthermore, we will make available HeidelTime resources for Arabic, Italian, and Vietnamese (HeidelTime, 2013).",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Conclusions & Ongoing Work",
"sec_num": "5"
},
{
"text": "For further details on HeidelTime's rule syntax, its domaindependent normalization strategies, and its architecture in general, we refer toStr\u00f6tgen and Gertz (2012a).",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "",
"sec_num": null
}
],
"back_matter": [],
"bib_entries": {
"BIBREF0": {
"ref_id": "b0",
"title": "Temporal Information Retrieval: Challenges and Opportunities",
"authors": [
{
"first": "Omar",
"middle": [],
"last": "Alonso",
"suffix": ""
},
{
"first": "Jannik",
"middle": [],
"last": "Str\u00f6tgen",
"suffix": ""
},
{
"first": "Ricardo",
"middle": [],
"last": "Baeza-Yates",
"suffix": ""
},
{
"first": "Michael",
"middle": [],
"last": "Gertz",
"suffix": ""
}
],
"year": 2011,
"venue": "Proceedings of the 1st International Temporal Web Analytics Workshop",
"volume": "",
"issue": "",
"pages": "1--8",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Omar Alonso, Jannik Str\u00f6tgen, Ricardo Baeza-Yates, and Michael Gertz. 2011. Temporal Information Re- trieval: Challenges and Opportunities. In Proceedings of the 1st International Temporal Web Analytics Work- shop (TWAW 2011), pages 1-8.",
"links": null
},
"BIBREF2": {
"ref_id": "b2",
"title": "Merging Temporal Annotations",
"authors": [
{
"first": "Hector",
"middle": [],
"last": "Llorens",
"suffix": ""
},
{
"first": "Naushad",
"middle": [],
"last": "Uzzaman",
"suffix": ""
},
{
"first": "James",
"middle": [
"F"
],
"last": "Allen",
"suffix": ""
}
],
"year": 2012,
"venue": "19th International Symposium on Temporal Representation and Reasoning",
"volume": "2012",
"issue": "",
"pages": "107--113",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Hector Llorens, Naushad UzZaman, and James F. Allen. 2012. Merging Temporal Annotations. In 19th Inter- national Symposium on Temporal Representation and Reasoning, TIME 2012, pages 107-113.",
"links": null
},
"BIBREF3": {
"ref_id": "b3",
"title": "Probabilistic Part-of-Speech Tagging Using Decision Trees",
"authors": [
{
"first": "Helmut",
"middle": [],
"last": "Schmid",
"suffix": ""
}
],
"year": 1994,
"venue": "Proceedings of the International Conference on New Methods in Language Processing",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Helmut Schmid. 1994. Probabilistic Part-of-Speech Tag- ging Using Decision Trees. In Proceedings of the In- ternational Conference on New Methods in Language Processing.",
"links": null
},
"BIBREF4": {
"ref_id": "b4",
"title": "HeidelTime: High Quality Rule-Based Extraction and Normalization of Temporal Expressions",
"authors": [
{
"first": "Jannik",
"middle": [],
"last": "Str\u00f6tgen",
"suffix": ""
},
{
"first": "Michael",
"middle": [],
"last": "Gertz",
"suffix": ""
}
],
"year": 2010,
"venue": "Proceedings of the 5th International Workshop on Semantic Evaluation (SemEval'10)",
"volume": "",
"issue": "",
"pages": "321--324",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Jannik Str\u00f6tgen and Michael Gertz. 2010. HeidelTime: High Quality Rule-Based Extraction and Normaliza- tion of Temporal Expressions. In Proceedings of the 5th International Workshop on Semantic Evaluation (SemEval'10), pages 321-324.",
"links": null
},
"BIBREF5": {
"ref_id": "b5",
"title": "Multilingual and Cross-domain Temporal Tagging. Language Resources and Evaluation",
"authors": [
{
"first": "Jannik",
"middle": [],
"last": "Str\u00f6tgen",
"suffix": ""
},
{
"first": "Michael",
"middle": [],
"last": "Gertz",
"suffix": ""
}
],
"year": 2012,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Jannik Str\u00f6tgen and Michael Gertz. 2012a. Multilingual and Cross-domain Temporal Tagging. Language Re- sources and Evaluation, Online first.",
"links": null
},
"BIBREF6": {
"ref_id": "b6",
"title": "Temporal Tagging on Different Domains: Challenges, Strategies, and Gold Standards",
"authors": [
{
"first": "Jannik",
"middle": [],
"last": "Str\u00f6tgen",
"suffix": ""
},
{
"first": "Michael",
"middle": [],
"last": "Gertz",
"suffix": ""
}
],
"year": 2012,
"venue": "Proceedings of the 8th International Conference on Language Resources and Evaluation",
"volume": "",
"issue": "",
"pages": "3746--3753",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Jannik Str\u00f6tgen and Michael Gertz. 2012b. Temporal Tagging on Different Domains: Challenges, Strate- gies, and Gold Standards. In Proceedings of the 8th International Conference on Language Resources and Evaluation, pages 3746-3753.",
"links": null
},
"BIBREF7": {
"ref_id": "b7",
"title": "An Event-centric Model for Multilingual Document Similarity",
"authors": [
{
"first": "Jannik",
"middle": [],
"last": "Str\u00f6tgen",
"suffix": ""
},
{
"first": "Michael",
"middle": [],
"last": "Gertz",
"suffix": ""
},
{
"first": "Conny",
"middle": [],
"last": "Junghans",
"suffix": ""
}
],
"year": 2011,
"venue": "Proceeding of the 34rd International ACM SIGIR Conference on Research and Development in Information Retrieval (SIGIR'11)",
"volume": "",
"issue": "",
"pages": "953--962",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Jannik Str\u00f6tgen, Michael Gertz, and Conny Junghans. 2011. An Event-centric Model for Multilingual Doc- ument Similarity. In Proceeding of the 34rd Interna- tional ACM SIGIR Conference on Research and De- velopment in Information Retrieval (SIGIR'11), pages 953-962.",
"links": null
},
"BIBREF8": {
"ref_id": "b8",
"title": "TempEval-3: Evaluating Events, Time Expressions",
"authors": [
{
"first": "Naushad",
"middle": [],
"last": "Uzzaman",
"suffix": ""
},
{
"first": "Hector",
"middle": [],
"last": "Llorens",
"suffix": ""
},
{
"first": "James",
"middle": [
"F"
],
"last": "Allen",
"suffix": ""
},
{
"first": "Leon",
"middle": [],
"last": "Derczynski",
"suffix": ""
},
{
"first": "Marc",
"middle": [],
"last": "Verhagen",
"suffix": ""
},
{
"first": "James",
"middle": [],
"last": "Pustejovsky",
"suffix": ""
}
],
"year": 2012,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Naushad UzZaman, Hector Llorens, James F. Allen, Leon Derczynski, Marc Verhagen, and James Puste- jovsky. 2012. TempEval-3: Evaluating Events, Time Expressions, and Temporal Relations. CoRR, abs/1206.5333.",
"links": null
},
"BIBREF9": {
"ref_id": "b9",
"title": "SemEval-2010 Task 13: TempEval-2",
"authors": [
{
"first": "Marc",
"middle": [],
"last": "Verhagen",
"suffix": ""
},
{
"first": "Roser",
"middle": [],
"last": "Sauri",
"suffix": ""
},
{
"first": "Tommaso",
"middle": [],
"last": "Caselli",
"suffix": ""
},
{
"first": "James",
"middle": [],
"last": "Pustejovsky",
"suffix": ""
}
],
"year": 2010,
"venue": "Proceedings of the 5th International Workshop on Semantic Evaluation (Sem-Eval'10)",
"volume": "",
"issue": "",
"pages": "57--62",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Marc Verhagen, Roser Sauri, Tommaso Caselli, and James Pustejovsky. 2010. SemEval-2010 Task 13: TempEval-2. In Proceedings of the 5th In- ternational Workshop on Semantic Evaluation (Sem- Eval'10), pages 57-62.",
"links": null
}
},
"ref_entries": {
"TABREF0": {
"type_str": "table",
"num": null,
"html": null,
"text": "81.69 80.92 90.85 92.57 91.7 72.37 83.32 bug-fixed 77.56 81.17 79.32 88.28 92.40 90.30 70.21 82.03 1.2 73.32 81.17 77.05 83.46 92.40 87.70 67.87 79.67",
"content": "<table><tr><td/><td colspan=\"3\">strict match</td><td colspan=\"3\">relaxed match</td><td>normalization</td></tr><tr><td>a) Aquaint</td><td>P</td><td>R</td><td>F1</td><td>P</td><td>R</td><td>F1</td><td>value type</td></tr><tr><td colspan=\"2\">tuned 80.17 b) TimeBank P</td><td>R</td><td>F1</td><td>P</td><td>R</td><td>F1</td><td>value type</td></tr><tr><td>tuned</td><td colspan=\"7\">85.39 84.15 84.76 92.16 90.83 91.49 79.01 88.74</td></tr><tr><td>bug-fixed</td><td colspan=\"7\">83.17 82.70 82.94 90.86 90.35 90.60 76.24 87.78</td></tr><tr><td>1.2</td><td colspan=\"7\">82.89 82.62 82.76 90.72 90.43 90.57 76.39 87.75</td></tr><tr><td>c) Spanish</td><td>P</td><td>R</td><td>F1</td><td>P</td><td>R</td><td>F1</td><td>value type</td></tr><tr><td>new</td><td colspan=\"7\">90.53 81.26 85.65 96.23 86.38 91.04 84.10 89.40</td></tr></table>"
},
"TABREF1": {
"type_str": "table",
"num": null,
"html": null,
"text": "Results on training data ranked by value F1.",
"content": "<table/>"
},
"TABREF2": {
"type_str": "table",
"num": null,
"html": null,
"text": "78.99 81.34 93.08 87.68 90.30 77.61 82.09 bug-fixed 80.77 76.09 78.36 90.00 84.78 87.31 72.39 79.10 1.2 80.15 76.09 78.07 89.31 84.78 86.99 72.12 78.81 next best* 78.72 80.43 79.57 89.36 91.30 90.32 70.97 80.29 HeidelTime 90.91 80.40 85.33 96.02 84.92 90.13 85.33 87.47 TipSemB 88.51 77.39 82.57 93.68 81.91 87.40 71.85 82.04 jrc-1/2 65.83 39.70 49.53 86.67 52.26 65.20 50.78 62.70",
"content": "<table><tr><td/><td colspan=\"3\">strict match</td><td colspan=\"3\">relaxed match</td><td>normalization</td></tr><tr><td>a) English</td><td>P</td><td>R</td><td>F1</td><td>P</td><td>R</td><td>F1</td><td>value type</td></tr><tr><td colspan=\"2\">tuned 83.85 b) Spanish P</td><td>R</td><td>F1</td><td>P</td><td>R</td><td>F1</td><td>value type</td></tr></table>"
},
"TABREF3": {
"type_str": "table",
"num": null,
"html": null,
"text": "TempEval-3 task A evaluation results ranked by value F1 (* next best: NavyTime).",
"content": "<table/>"
}
}
}
} |