{ "paper_id": "2021", "header": { "generated_with": "S2ORC 1.0.0", "date_generated": "2023-01-19T03:11:15.619243Z" }, "title": "Date and Time in Universal Dependencies", "authors": [ { "first": "Daniel", "middle": [], "last": "Zeman", "suffix": "", "affiliation": { "laboratory": "", "institution": "Charles University", "location": { "settlement": "Prague" } }, "email": "zeman@ufal.mff.cuni.cz" } ], "year": "", "venue": null, "identifiers": {}, "abstract": "We attempt to shed some light on the various ways how languages specify date and time, and on the options we have when trying to annotate them uniformly across Universal Dependencies. Examples from several language families are discussed, and their annotation is proposed. Our hope is to eventually make this (or similar) proposal an integral part of the UD annotation guidelines, which would help improve consistency of the UD treebanks. The current annotations are far from consistent, as can be seen from the survey we provide in appendices to this paper.", "pdf_parse": { "paper_id": "2021", "_pdf_hash": "", "abstract": [ { "text": "We attempt to shed some light on the various ways how languages specify date and time, and on the options we have when trying to annotate them uniformly across Universal Dependencies. Examples from several language families are discussed, and their annotation is proposed. Our hope is to eventually make this (or similar) proposal an integral part of the UD annotation guidelines, which would help improve consistency of the UD treebanks. The current annotations are far from consistent, as can be seen from the survey we provide in appendices to this paper.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Abstract", "sec_num": null } ], "body_text": [ { "text": "The label of the UTC time zone 1 suggests that time can be coordinated and universal. Unfortunately, date and time expressions in the world's languages are not universal, and their current annotation in the various corpora in Universal Dependencies (UD) (de Marneffe et al., 2021) 2 is far from coordinated. One likely reason is that from the point of view of a grammarian, date and time expressions are a rather marginal phenomenon. Similarly, they are not the first thing to be covered by corpus annotation guidelines\u037e and sometimes there are no guidelines for them at all. To the best of our knowledge, this is the case of Universal Dependencies, at least of the universal part of the UD guidelines 3 (we cannot exclude that one of the language-specific sections discusses these expressions). The issue has been discussed in the UD Github issue tracker 4,5 but the discussion did not result in a concrete specification in the guidelines. No coherent proposal seems to have emerged, neither on the website nor in UD-related papers (de Marneffe et al., 2021\u037e Nivre et al., 2016\u037e Nivre et al., 2020 . A noteworthy exception is the recent proposal by Schneider and Zeldes (2021, Section 5) , who try to solve dates in English.", "cite_spans": [ { "start": 1054, "end": 1098, "text": "2021\u037e Nivre et al., 2016\u037e Nivre et al., 2020", "ref_id": null }, { "start": 1150, "end": 1188, "text": "Schneider and Zeldes (2021, Section 5)", "ref_id": null } ], "ref_spans": [], "eq_spans": [], "section": "Introduction", "sec_num": "1" }, { "text": "The main research question is whether (or to what extent) date and time expressions have internal syntactic structure. UD is a syntactic framework, so in clear cases of syntactic structure we should annotate it analogously to similar constructions elsewhere in the language. On the other hand, date and time expressions are frequent in certain genres across the world's languages, with globally understood semantics, so it would be beneficial for language-understanding applications to always organize the corresponding items (year, month, day, hour, minute\u2026) the same way. Ideally, we would like to find a rule that is language-independent, yet it does not clash with morphosyntax when applied to concrete languages.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Introduction", "sec_num": "1" }, { "text": "Date and time expressions are difficult not only because of their (understudied) grammatical peculiarity, but also because of the way they are encoded in written language. If the expression involves digits and symbols, the general guiding principle in UD is that the analysis should be parallel to how the expression is pronounced and how it would appear in a treebank of spoken language (de Marneffe et al., 2021, p. 285) . Therefore, another research question of this paper is to what extent this principle can actually be followed, as in some cases there are multiple possible readings.", "cite_spans": [ { "start": 388, "end": 422, "text": "(de Marneffe et al., 2021, p. 285)", "ref_id": null } ], "ref_spans": [], "eq_spans": [], "section": "Introduction", "sec_num": "1" }, { "text": "In the present study, we survey various time-related expressions in a selection of the UD languages and their internal syntactic structure (if any). We then propose a solution: a set of guidelines thatif added to the UD documentation -would make annotation of these expressions easier and hopefully more consistent. The current annotation in UD treebanks is not discussed directly in the survey, but for basic date expressions, an overview is provided in the appendices. With typological diversity in mind, we conduct the research on 5 languages from 4 different families.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Introduction", "sec_num": "1" }, { "text": "If a date refers to the month by its name, then the day and year numbers are separate tokens, too. However, if the date consists entirely of numbers and punctuation, some UD treebanks prefer to treat the date as a single token. This is not exactly wrong (and it helps avoid some of the issues we are going to discuss in this paper), yet we would argue that splitting the date into multiple tokens can increase the parallelism with dates where the month is named. Furthermore, the orthographic rules in some languages allow writing numerical dates with or without spaces, 6 which would lead to inconsistent annotation if the dates without spaces are not split.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Tokenization", "sec_num": "2" }, { "text": "Punctuation separators such as slashes or hyphens should be independent tokens, too. However, if there are periods that, according to the language-specific rules, 7 mark the numbers as ordinal numerals, we recommend to keep them in the same token as the number. The token will then be recognizable as an ordinal numeral, and it will be parallel to English 1st, 2nd, 3rd, 4th\u2026 It is less obvious whether a similar argument should be made for time expressions. The core part, hours and minutes, are typically spelled as one string, looking like a decimal number (although they actually use the sexagesimal system, and sometimes a different punctuation symbol). There are multiple options how to pronounce it, but it is not uncommon that the hour and minute parts are simply read as a sequence of two numbers. We suggest to keep such numbers as one token. 8 However, if the string contains unit names or abbreviations, it should be better split into multiple tokens: 19h15m would become 19 h 15 m.", "cite_spans": [ { "start": 348, "end": 360, "text": "English 1st,", "ref_id": null }, { "start": 361, "end": 365, "text": "2nd,", "ref_id": null }, { "start": 366, "end": 370, "text": "3rd,", "ref_id": null }, { "start": 371, "end": 375, "text": "4th\u2026", "ref_id": null } ], "ref_spans": [], "eq_spans": [], "section": "Tokenization", "sec_num": "2" }, { "text": "Names of months and days of week are considered proper names (PROPN) in some languages and common nouns (NOUN) in others. Sometimes the distinction is just in language-internal orthographical rules (whether or not the word is written capitalized), sometimes there may be deeper consequences, e.g., whether the word is used with a definite article. The decision has to be made on a per-language basis\u037e if there are no reasons supporting PROPN, we suggest to use NOUN as the default.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Tags and Features", "sec_num": "3" }, { "text": "Tokens consisting entirely of digits (i.e., years and sometimes days) should always be tagged as cardinal numerals (NUM). However, sometimes the form of the number clearly indicates that it should be pronounced as an ordinal numeral (5 th , 5.). Ordinals are a subclass of adjectives in UD, hence the ADJ tag should be used. Note that the POS category is not changed to noun when the numeral heads a nominal. According to the UD tagging principles, the nominal function is encoded in the incoming dependency relation but the POS tag stays the same.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Tags and Features", "sec_num": "3" }, { "text": "In the UD taxonomy of syntactic units, dates are nominals. Most often they function as temporal oblique modifiers in clauses (obl:tmod), as in The data will be released on November 15, 2021, or even without a preposition (It took place last April). However, dates can appear in all other constructions where nominals can. They can be non-temporal modifiers (What did they say about June 30?), subjects (June 30 suits me perfectly) etc.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Dates", "sec_num": "4" }, { "text": "Two date patterns are common in English: May 15, 2015 (pronounced May (the) fifteenth, twenty fifteen / two thousand (and) fifteen) and 15 May 2015 (pronounced the fifteenth of May twenty fifteen / two thousand (and) fifteen). In both cases, the day may be spelled so that the ordinal numeral is overtly marked: May 15th, 2015. The pronunciation of the day-month-year pattern with the preposition of shows that the month modifies the day and not vice versa\u037e we should treat the written date as it is pronounced, even though the preposition is not visible (cf. (de Marneffe et al., 2021, p. 285) ). The month is a temporal nominal modifier, nmod:tmod. 9 Similar patterns occur in some other European languages, such as Spanish (el quince de mayo, lit. the fifteen of May).", "cite_spans": [ { "start": 560, "end": 594, "text": "(de Marneffe et al., 2021, p. 285)", "ref_id": null } ], "ref_spans": [], "eq_spans": [], "section": "English", "sec_num": "4.1" }, { "text": "The situation is less clear with the month-day-year pattern. Schneider and Zeldes (2021) propose to make the day the head here, too, since the month can be omitted with sufficient context (I'll see you on the fifteenth)\u037e if we wanted to omit the day instead, the case marker would have to change (I'll see you in June). While this argumentation probably makes sense in English (no surface signals that the day modifies the month, parallel structure with the first pattern), note that the omission of the month could also be explained as ellipsis, and then the standard UD solution would be to promote the day to the head position (if the rule were that normally the month is the head).", "cite_spans": [ { "start": 61, "end": 88, "text": "Schneider and Zeldes (2021)", "ref_id": "BIBREF6" } ], "ref_spans": [], "eq_spans": [], "section": "English", "sec_num": "4.1" }, { "text": "An analogous argument can be made about the year. It can be omitted from the full date (on May 15(, 2015)) but it cannot occur with the day and without the month (*on the fifteenth, 2015). We take this as evidence that the year modifies the month, rather than the day-month complex as a whole, and it should be attached to the month. Here we disagree with Schneider and Zeldes (2021) , who attach the year to the day. In either case the relation is not nummod because the year is a label that does not express quantity (cf. (de Marneffe et al., 2021, p. 285) ). It is a temporal nominal modifier, nmod:tmod. An optional era specifier (BC/AD) will be attached as nmod:tmod to the year.", "cite_spans": [ { "start": 356, "end": 383, "text": "Schneider and Zeldes (2021)", "ref_id": "BIBREF6" }, { "start": 519, "end": 558, "text": "(cf. (de Marneffe et al., 2021, p. 285)", "ref_id": null } ], "ref_spans": [], "eq_spans": [], "section": "English", "sec_num": "4.1" }, { "text": "Note that the year can appear with the month and without the day if the case marker is changed: in May 2015. Both in May and in 2015 are grammatical\u037e however, in the right context, in May has the same meaning as in May 2015 while in 2015 refers to a longer period. Therefore we propose to attach the year as a dependent of the month. Furthermore, it is also parallel to expressions where of is overtly used: ", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "English", "sec_num": "4.1" }, { "text": "In Czech, the standard word order is day-month-year: 15. kv\u011btna 2015 (pronounced patn\u00e1ct\u00e9ho kv\u011btna dva tis\u00edce patn\u00e1ct, lit. fifteenth.Gen May.Gen 2015.Nom). The day is an ordinal numeral (ADJ) but unlike in English, it modifies the noun that denotes the month. This is semantically slightly odd (we are referring to the fifteenth day of May, not to a fifteenth May in a sequence of Mays), and it likely stems from a longer expression \"the fifteenth day of May\", but the morphosyntactic behavior has developed to that of regular adjectival modifiers. The day adjective thus agrees with the month in gender, number, and case. In the example above both of them have the genitive form, which is the default for temporal oblique modifiers, but both of them will switch to the nominative if the date is used as a subject, accusative if used as an object etc. The above reasoning does not work so much when the month is encoded numerically: 15. 5. 2015. It is conventionally pronounced patn\u00e1ct\u00e9ho p\u00e1t\u00fd dva tis\u00edce patn\u00e1ct, lit. fifteenth.Gen fifth.Nom 2015.Nom, that is, there are two ordinals (plus the year cardinal) and they no longer agree in case. We do not have an explanation for this reading\u037e nevertheless, in the absence of morphosyntactic evidence for one of the possible analyses, we propose to use a parallel structure to that of spelled-out month, i.e., the month is the head. The only change is the label of the first dependency, nmod:tmod instead of amod:tmod, as the relation does not behave like standard adjectival modification in Czech. ", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Czech", "sec_num": "4.2" }, { "text": "The most frequent date form in Finnish is 15. toukokuuta 2015, pronounced viidestoista toukokuuta kaksituhattaviisitoista, lit. fifteenth.Nom May.Par 2015.Nom. The day number is ordinal (ADJ) and it does not agree in case with the month name\u037e instead, it forces the month name into the partitive form. We take this as a sign that the month depends on the day, like in English and unlike in Czech. The partitive case is used also when the month is spelled and pronounced as an ordinal number: 15.5.2015, pronounced viidestoista viidett\u00e4 kaksituhattaviisitoista. A month name with year (but without the day number) is typically found in the inessive case (toukokuussa 2015 \"in May 2015\") but can occur in other cases if they are required by the surrounding syntactic context. Their relation should be nmod:tmod because the number does not specify a quantity of months. Finnish also has an alternative date pattern, common in informal and spoken situations, where the month precedes the day. Here the month must be in the genitive case and the day takes the essive form. The day ordinal is optionally followed by the word \"day\", also in essive: toukokuun viidenten\u00e4toista (p\u00e4iv\u00e4n\u00e4). Another option is that the day ordinal and the word \"day\" are in nominative: toukokuun viidestoista p\u00e4iv\u00e4. Here the day ordinal modifies p\u00e4iv\u00e4 and agrees with it in case. Finally, it is also possible to encounter date expressions that feature the word p\u00e4iv\u00e4 \"day\" but the preceding number is not properly marked as ordinal (the period is missing): 15 p\u00e4iv\u00e4n\u00e4 toukokuuta 2015. We acknowledge that it may then be tagged as a cardinal, although it may be pronounced as an ordinal (viidenten\u00e4toista \"fifteenth.Ess\" instead of viiten\u00e4toista \"fifteen.Ess\"). The relation from p\u00e4iv\u00e4n\u00e4 can be nmod:tmod but not nummod. ", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Finnish", "sec_num": "4.3" }, { "text": "In Indonesian, dates are often introduced by the word tanggal \"date\": pada tanggal 15 Mei 2015, pronounced pada tanggal lima belas Mei dua ribu lima belas, lit. on date five -teen May two thousand five -teen. The day and year numbers are cardinal (rather than ordinal) numerals. As always, they do not denote quantity of anything, so they should not be attached via nummod. There are no morphological clues that would enlighten the relation between the day and the month, so a flat analysis seems appealing. Nevertheless, we can at least repeat what Schneider and Zeldes (2021) said about English. The month can be omitted and we can say pada tanggal lima belas \"on the fifteenth\". If that leads to making the day the head in English, we should make the Indonesian analysis parallel and attach the month to the day as nmod:tmod. The year, if present, will be attached to the month, and the optional era specifier modifies the year. Modifiers such as lalu \"last\" and mendatang \"next\" are tagged ADJ in some treebanks and VERB in others (last = passed, next = coming). Of course, this should be harmonized, but the adjective-verb distinction is beyond the scope of this paper. If the modifier is a verb, it is a relative adnominal clause (\"that has passed\") and should be attached as acl:relcl. Otherwise it is a simple adjectival modifier, amod. In tahun lalu \"last year\", lalu modifies tahun. We could also say 15 Mei lalu \"last May 15\", which may or may not be in the previous year, and it is typically both the fifteenth day of the last May, and the last fifteenth of May. Hence both the day and the month could serve as the parent node, and in the absence of other criteria, we propose to attach the modifier high: ", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Indonesian", "sec_num": "4.4" }, { "text": "In Chinese, dates proceed from the least specific to the most specific item. Numbers are always accompanied by the nouns for \"year\", \"month\" and \"day\"\u037e there are no names for months, they are encoded simply as a number + \"month\". Years are normally written using Western Arabic digits. Months and days either use Arabic digits, too, or they are written in Chinese characters. Examples: 2015\u5e745\u670815\u65e5 (2015 ni\u00e1n 5 yu\u00e8 15 r\u00ec, pronounced \u00e8r l\u00edng y\u012b w\u01d4 ni\u00e1n w\u01d4 yu\u00e8 sh\u00edw\u01d4 r\u00ec), lit. two zero one five year five month fifteen day\u037e \u4e94\u6708\u5341\u4e94\u65e5 (w\u01d4 yu\u00e8 sh\u00edw\u01d4 r\u00ec) \"May 15\". The numerals are cardinal and modify the respective nouns, but their relation should be nmod:tmod rather than nummod, as they do not denote quantity. Similarly to Indonesian, there are hardly any criteria that would favor one of the three items as the head. We therefore propose an analysis that is parallel to Indonesian and English, i.e., the less specific item depends on the more specific one. An era specifier, if present, modifies the year expression and is attached to its head noun. The year number may be substituted by an expression such as \u540c\u5e74 (t\u00f3ngni\u00e1n) \"same year\", \u6b21\u5e74 (c\u00ecni\u00e1n) \"following year\" etc. ", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Chinese", "sec_num": "4.5" }, { "text": "We propose in Section 2 that time expressed using digits be one token, as in the following example (copied from Schneider and Zeldes (2021)). Schneider and Zeldes also propose that if the time is written as ten o'clock, the token o'clock should be considered an adverb and advmod of ten. Note that in English, Czech, Finnish and Indonesian, the prepositions indicate which part is the modifier. In Chinese, we have two numbers with units. Unlike in dates, the nummod analysis is quite appropriate here, as we are counting hours (and minutes). This is not the case in Indonesian, where sepuluh jam \"ten hours\" is nummod (indicating duration) but jam sepuluh (lit. the hour ten) is nmod:tmod (labeling the hour). The relation between the Chinese hours and minutes cannot be characterized as subordination, hence we propose conj instead of nmod:tmod (nine hours [and] forty-five minutes\u037e another possible candidate would be flat).", "cite_spans": [ { "start": 859, "end": 864, "text": "[and]", "ref_id": null } ], "ref_spans": [], "eq_spans": [], "section": "Time", "sec_num": "6" }, { "text": "If time occurs together with date (it happened on May 15 at 9:45), they are often two independent modifiers -note that in the previous English example, each has its own preposition. However, there are situations where date and time have to be considered as one unit, denoting a point in time, which has a syntactic function in the sentence: What about July 12, between 1:30 and 4:00. It is not obvious whether the date or the time should serve as the head in such cases. In this particular English example, we could say that the preposition about belongs to the date, hence the following analysis: There are several options how to analyze ranges. Two full date expressions with different prepositions (from and to) could be quite naturally annotated as two sibling oblique modifiers of the same clause. Cases where only a part of the date is ranged (e.g., the month in from May to November 2015) could be handled as ellipsis (i.e., the first modifier would be from May and the second would be to November 2015). Analogously with a dash, the first expression would be May and the second -November 2015.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Time", "sec_num": "6" }, { "text": "This solution has the disadvantage that the partial first expression is detached from the shared part, so it is more difficult to infer that May actually refers to May 2015. Another option is to attach the closing part of the range to the opening part\u037e for partial ranges, only the ranged parts can be connected, and the shared, less specific part is attached to the head. This approach is currently taken in some UD treebanks\u037e 11 however, if the closing part has a preposition (either spelled out, or assumed to be encoded by the dash), the annotators mechanically pick the nmod relation, which seems wrong. The second date does not really modify the first date. Their relation is much closer to coordination: the event occurs on both the dates (as well as on all dates in between). In fact, some languages use conjunctions instead of (or in addition to) prepositions to express ranges: German Mai bis November, Czech kv\u011bten a\u017e listopad \"May to November\". Treating the prepositional (from-to) cases as coordination would have the advantage of better parallelism and it would solve the shared modifier problem (from May to November 2015 would be analogous to either May or November 2015). Coordinating May with November would allow 2015 to technically modify the first conjunct but be propagated in enhanced UD to the second conjunct. 12 We lean towards the coordination analysis as the most parallel and cross-linguistically applicable solution. If that is not accepted by the UD community, then we think that attaching the two endpoints as siblings is better than making one of them an nmod of the other. We provide a survey of annotation patterns in the UD 2.8 treebanks of English, Czech, Finnish, Indonesian and Chinese in the appendices. Some treebanks are internally consistent, some less so, but there is very little consensus across treebanks of the same language. It is thus obvious that any improvement would be welcome, even if it cannot be done perfectly.", "cite_spans": [ { "start": 1335, "end": 1337, "text": "12", "ref_id": null } ], "ref_spans": [], "eq_spans": [], "section": "Time", "sec_num": "6" }, { "text": "Fortunately, it is not necessary to re-annotate all UD treebanks manually. Language-specific patterns can be designed that will find (almost) all occurrences of date and time expressions in a treebank, 13 and identify their parts. The annotation can then be harmonized using tree-rewriting systems such as Udapi (Popel et al., 2017) or Grew (Guillaume, 2021) .", "cite_spans": [ { "start": 202, "end": 204, "text": "13", "ref_id": null }, { "start": 312, "end": 332, "text": "(Popel et al., 2017)", "ref_id": "BIBREF4" }, { "start": 341, "end": 358, "text": "(Guillaume, 2021)", "ref_id": "BIBREF1" } ], "ref_spans": [], "eq_spans": [], "section": "Time", "sec_num": "6" }, { "text": "We have surveyed various date/time-related expressions in five languages from four different language families. We have shown that some of these expressions in some languages have internal morphosyntactic structure, which should be observed when constructing their UD analysis. The syntactic structure of semantically corresponding expressions is not always compatible across language boundaries, hence the annotation rules cannot be language-independent. However, in cases where no underlying syntax can be detected, we recommend one of the annotation options as the default solution.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Conclusion", "sec_num": "9" }, { "text": "We believe that it is necessary to add some guidelines for date and time expressions to the UD documentation, as it will greatly improve consistency of the UD data (these expressions are quite frequent in some genres). We also believe that with language-specific heuristics, the data can be fixed relatively easily, using existing tools for automatic modification of the dependency structures.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Conclusion", "sec_num": "9" }, { "text": "We provide an overview of date annotations currently applied in the English UD treebanks. The survey demonstrates the variability of dependency relations. There are further differences in POS tags and features but they are not shown here. We only show dates, i.e., without days of week, without times, no ranges etc. Sometimes the same pattern receives multiple annotations within the same treebank. Other treebanks are more consistent internally, yet the approaches differ heavily across treebanks.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "A Survey of English Date Annotations in UD 2.8", "sec_num": null }, { "text": "The total numbers of occurrences in the tables are approximate. Some marginal cases with extra dependents are either clustered with more generic patterns or omitted from the table completely. ", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "A Survey of English Date Annotations in UD 2.8", "sec_num": null }, { "text": "For instance, in Czech, the default is with spaces after periods but the standard admits an alterative format without spaces in business and technical documents (https://prirucka.ujc.cas.cz/?ref=160&id=810).7 E.g. in Czech, German and Finnish. 8 It could be argued that the read-out-loud rule leads to multiple tokens for 7:15 because seven fifteen is written as two tokens. However, we do not think it would be useful to extend this rule to purely numerical strings because then we would have to split also numbers that do not denote time.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "", "sec_num": null }, { "text": "The current practice in English UD seems to be that the :tmod subtype is only used when there is no preposition, as a kind of justification why there is nmod without case. We believe that it is equally useful to use it for prepositional temporal modifiers. Similarly, advmod:tmod could be used instead of plain advmod for time-related adverbs, as it is currently used in some other UD languages. However, regardless of how broadly they are applied, relation subtypes are always optional in UD.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "", "sec_num": null }, { "text": "There are also German examples where the month is in the genitive and modifies the dative day ordinal: am F\u00fcnfzehnten des Monats \"on the fifteenth of the month\".", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "", "sec_num": null }, { "text": "In fact, this approach also matches example (49) of (de Marneffe et al., 2021).12 As one of the reviewers pointed out, the correlative expression from X to Y is certainly a grammaticalized construction (it cannot be paraphrased as to November from May), and the constituents need not be nominals (Heights range from tall to short, etc.), reminiscent of coordination. See(Reynolds and Pullum, 2013) for an argument that versus has grammaticalized from a preposition to a coordinator.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "", "sec_num": null } ], "back_matter": [ { "text": "This work was supported by the grants 20-16819X (LUSyD) of the Czech Science Foundation\u037e and LM2018101 (LINDAT/CLARIAH-CZ) of the Ministry of Education, Youth, and Sports of the Czech Republic.We thank the anonymous reviewers for very useful comments.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Acknowledgements", "sec_num": null } ], "bib_entries": { "BIBREF0": { "ref_id": "b0", "title": "Universal Dependencies", "authors": [ { "first": "Marie-Catherine", "middle": [], "last": "De Marneffe", "suffix": "" }, { "first": "Christopher", "middle": [], "last": "Manning", "suffix": "" }, { "first": "Joakim", "middle": [], "last": "Nivre", "suffix": "" }, { "first": "Daniel", "middle": [], "last": "Zeman", "suffix": "" } ], "year": 2021, "venue": "Computational Linguistics", "volume": "47", "issue": "2", "pages": "255--308", "other_ids": {}, "num": null, "urls": [], "raw_text": "Marie-Catherine de Marneffe, Christopher Manning, Joakim Nivre, and Daniel Zeman. 2021. Universal Depen- dencies. Computational Linguistics, 47(2):255-308.", "links": null }, "BIBREF1": { "ref_id": "b1", "title": "Graph matching and graph rewriting: Grew tools for corpus exploration, maintenance and conversion", "authors": [ { "first": "Bruno", "middle": [], "last": "Guillaume", "suffix": "" } ], "year": 2021, "venue": "Proceedings of the 16th Conference of the European Chapter of the Association for Computational Linguistics: System Demonstrations", "volume": "", "issue": "", "pages": "168--175", "other_ids": {}, "num": null, "urls": [], "raw_text": "Bruno Guillaume. 2021. Graph matching and graph rewriting: Grew tools for corpus exploration, maintenance and conversion. In Proceedings of the 16th Conference of the European Chapter of the Association for Compu- tational Linguistics: System Demonstrations, pages 168-175.", "links": null }, "BIBREF2": { "ref_id": "b2", "title": "Universal Dependencies v1: A multilingual treebank collection", "authors": [ { "first": "Joakim", "middle": [], "last": "Nivre", "suffix": "" }, { "first": "Marie-Catherine", "middle": [], "last": "De Marneffe", "suffix": "" }, { "first": "Filip", "middle": [], "last": "Ginter", "suffix": "" }, { "first": "Yoav", "middle": [], "last": "Goldberg", "suffix": "" }, { "first": "Jan", "middle": [], "last": "Haji\u010d", "suffix": "" }, { "first": "Christopher", "middle": [ "D" ], "last": "Manning", "suffix": "" }, { "first": "Ryan", "middle": [], "last": "Mcdonald", "suffix": "" }, { "first": "Slav", "middle": [], "last": "Petrov", "suffix": "" }, { "first": "Sampo", "middle": [], "last": "Pyysalo", "suffix": "" }, { "first": "Natalia", "middle": [], "last": "Silveira", "suffix": "" }, { "first": "Reut", "middle": [], "last": "Tsarfaty", "suffix": "" }, { "first": "Daniel", "middle": [], "last": "Zeman", "suffix": "" } ], "year": 2016, "venue": "Proceedings of the 10th International Conference on Language Resources and Evaluation (LREC 2016)", "volume": "", "issue": "", "pages": "", "other_ids": {}, "num": null, "urls": [], "raw_text": "Joakim Nivre, Marie-Catherine de Marneffe, Filip Ginter, Yoav Goldberg, Jan Haji\u010d, Christopher D. Manning, Ryan McDonald, Slav Petrov, Sampo Pyysalo, Natalia Silveira, Reut Tsarfaty, and Daniel Zeman. 2016. Uni- versal Dependencies v1: A multilingual treebank collection. In Proceedings of the 10th International Confer- ence on Language Resources and Evaluation (LREC 2016), Portoro\u017e, Slovenia. European Language Resources Association.", "links": null }, "BIBREF3": { "ref_id": "b3", "title": "Universal Dependencies v2: An evergrowing multilingual treebank collection", "authors": [ { "first": "Joakim", "middle": [], "last": "Nivre", "suffix": "" }, { "first": "Marie-Catherine", "middle": [], "last": "De Marneffe", "suffix": "" }, { "first": "Filip", "middle": [], "last": "Ginter", "suffix": "" }, { "first": "Jan", "middle": [], "last": "Haji\u010d", "suffix": "" }, { "first": "Christopher", "middle": [], "last": "Manning", "suffix": "" }, { "first": "Sampo", "middle": [], "last": "Pyysalo", "suffix": "" }, { "first": "Sebastian", "middle": [], "last": "Schuster", "suffix": "" }, { "first": "Francis", "middle": [], "last": "Tyers", "suffix": "" }, { "first": "Daniel", "middle": [], "last": "Zeman", "suffix": "" } ], "year": 2020, "venue": "Proceedings of the 12th International Conference on Language Resources and Evaluation (LREC 2020)", "volume": "", "issue": "", "pages": "4034--4043", "other_ids": {}, "num": null, "urls": [], "raw_text": "Joakim Nivre, Marie-Catherine de Marneffe, Filip Ginter, Jan Haji\u010d, Christopher Manning, Sampo Pyysalo, Se- bastian Schuster, Francis Tyers, and Daniel Zeman. 2020. Universal Dependencies v2: An evergrowing mul- tilingual treebank collection. In Proceedings of the 12th International Conference on Language Resources and Evaluation (LREC 2020), pages 4034-4043, Marseille, France. European Language Resources Association.", "links": null }, "BIBREF4": { "ref_id": "b4", "title": "Udapi: Universal API for Universal Dependencies", "authors": [ { "first": "Martin", "middle": [], "last": "Popel", "suffix": "" }, { "first": "Zden\u011bk", "middle": [], "last": "\u017dabokrtsk\u00fd", "suffix": "" }, { "first": "Martin", "middle": [], "last": "Vojtek", "suffix": "" } ], "year": 2017, "venue": "Proceedings of the NoDaLiDa 2017 Workshop on Universal Dependencies", "volume": "", "issue": "", "pages": "96--101", "other_ids": {}, "num": null, "urls": [], "raw_text": "Martin Popel, Zden\u011bk \u017dabokrtsk\u00fd, and Martin Vojtek. 2017. Udapi: Universal API for Universal Dependen- cies. In Proceedings of the NoDaLiDa 2017 Workshop on Universal Dependencies (UDW 2017), pages 96-101, G\u00f6teborg, Sweden.", "links": null }, "BIBREF5": { "ref_id": "b5", "title": "New members of 'closed classes", "authors": [ { "first": "Brett", "middle": [], "last": "Reynolds", "suffix": "" }, { "first": "Geoffrey", "middle": [ "K" ], "last": "Pullum", "suffix": "" } ], "year": 2013, "venue": "", "volume": "", "issue": "", "pages": "", "other_ids": {}, "num": null, "urls": [], "raw_text": "Brett Reynolds and Geoffrey K. Pullum. 2013. New members of 'closed classes' in English. 02.", "links": null }, "BIBREF6": { "ref_id": "b6", "title": "Mischievous nominal constructions in Universal Dependencies", "authors": [ { "first": "Nathan", "middle": [], "last": "Schneider", "suffix": "" }, { "first": "Amir", "middle": [], "last": "Zeldes", "suffix": "" } ], "year": 2021, "venue": "Proceedings of the Fifth Workshop on Universal Dependencies", "volume": "", "issue": "", "pages": "", "other_ids": {}, "num": null, "urls": [], "raw_text": "Nathan Schneider and Amir Zeldes. 2021. Mischievous nominal constructions in Universal Dependencies. In Proceedings of the Fifth Workshop on Universal Dependencies (UDW, SyntaxFest 2021), Sofia, Bulgaria.", "links": null } }, "ref_entries": { "TABREF1": { "html": null, "content": "
10
nmod:tmod
amod:tmodnmod:tmoddetcasenmod:tmod
15.kv\u011btna2015n.l.v kv\u011btnu2015
15thMay2015ourerainMay2015
ADJNOUNNUMDETNOUNADP NOUNNUM
NumType=Ord Case=Gen NumType=Card Case=Gen Case=GenCase=Loc NumType=Card
", "type_str": "table", "text": "Similar patterns occur in some other European languages, such as German (am f\u00fcnfzehnten Mai, lit. on-the.Dat fifteenth.Dat May.Dat).", "num": null }, "TABREF7": { "html": null, "content": "
nmod:tmodnmod:tmodnmod:tmodnmod:tmod
casenmod:tmodnmod:tmodnmod:tmodnmod:tmodnmod:tmod
\u516c\u5143\u524d2015\u5e745\u670815\u65e5\u4e94\u6708\u5341\u4e94\u65e5
g\u014dngyu\u00e1nqi\u00e1n2015 ni\u00e1n5yu\u00e815r\u00ecw\u01d4yu\u00e8sh\u00edw\u01d4r\u00ec
com.-era before 2015 year5month15dayfive month fifteenday
NOUNADPNUM NOUN NUM NOUN NUM NOUNNUM NOUNNUMNOUN
nmod:tmod
nmod:tmod
\u540c\u5e745\u6708
t\u00f3ngni\u00e1n5yu\u00e8
same-year5month
NOUNNUM NOUN
5 Days of Week
appos
punctappos
nmod:tmodnmod:tmodpunct
Wednesday,May15May15,Wednesday
PROPNPUNCT PROPN NUMPROPN NUM PUNCTPROPN
", "type_str": "table", "text": "When the name of the day of week occurs together with the date, it can be understood as an apposition. Both expressions refer to the same day and they can be reordered. The first expression is treated as the technical head.", "num": null }, "TABREF12": { "html": null, "content": "
Pattern Patternnmod:tmod Proposal nmod:tmod nmod:tmod nmod:tmod nmod:tmod Proposal nmod:tmodnummod amod Total PUD Trees amod nummod flat nmod nummod nummod nmod Total PUD Trees nmod compoundnmod:tmod
Pattern 5/15/2015 15 May 15 May 2015 15th May 15th of May May 15 May 15, 2015 May 15, 2015 AD May 15th May 15th, 2015 the 15th of May A.2 GUM Pattern 15 May 15 May 2015 15th of May May 15 May 15, 2015 the 15th of May A.3 LinES Pattern Proposal Proposal 5 / 15 / 2015 nmod:tmod nmod:tmod punct punct 15 May nmod:tmod 15 May 2015 nmod:tmod nmod:tmod 15th May nmod:tmod 15th of May nmod:tmod case May 15 nmod:tmod May 15 , 2015 nmod:tmod nmod:tmod punct May 15 , 2015 AD nmod:tmod nmod:tmod punct nmod:tmod May 15th nmod:tmod May 15th , 2015 nmod:tmod nmod:tmod punct the 15th of May det nmod:tmod case Total GUM Trees Total EWT Trees 183 5/15/2015 (one token) 11 15 May nummod 20 15 May 2015 nummod nummod 15 May 2015 nummod nmod:tmod 3 15th May compound 15th May nummod 2 15th of May nmod case 80 May 15 nummod May 15 advmod 45 May 15 , 2015 nummod punct nummod 2 May 15 , 2015 AD nmod:tmod punct nummod nummod 23 May 15th nummod May 15th compound 5 May 15th , 2015 nummod nummod punct May 15th , 2015 nummod nummod punct May 15th , 2015 compound punct May 15th , 2015 compound punct 3 the 15th of May det nmod case the 15th of May det compound case 15 May nmod:tmod 4 15 May nmod:tmod 15 May compound 15 May 2015 nmod:tmod nmod:tmod 16 15 May 2015 nmod:tmod compound 15 May 2015 nmod:tmod nmod:tmod 15 May 2015 compoundnmod:tmod 15th of May nmod:tmod case 1 15th of May obl case May 15 nmod:tmod 21 May 15 compound May 15 nmod:tmod May 15 nummod May 15 , 2015 nmod:tmod nmod:tmod punct 82 May 15 , 2015 compound nmod:tmod punct May 15 , 2015 nmod:tmod nmod:tmod punct the 15th of May det nmod:tmod case 1 the 15th of May det obl case Proposal Total LinES Trees 15 May 15 May nmod:tmod 4 15 May amod 15 May, 2015 15 May , 2015 nmod:tmod nmod:tmod punct 2 15 May , 2015 amod nummod punct May 15 May 15 1 May 15 May 15, 2015 May 15 , 2015 nmod:tmod nmod:tmod punct 1 May 15 , 2015 nummod amod punct A.4 ParTUT Pattern Proposal Total ParTUT Trees 15 May 15 May nmod:tmod 5 15 May flat 15 May 2015 15 May 2015 nmod:tmod nmod:tmod 50 15 May 2015 flat flat 15 May of this year 15 May of this year nmod:tmod nmod:tmod case det 1 15 May of this year nmod flat case det May 15 May 15 nmod:tmod 1 May 15 flat May 15, 2015 May 15 , 2015 nmod:tmod nmod:tmod punct 5 May 15 , 2015 flat punct flat A.5 PUD Pattern Proposal Total PUD Trees 15 May 15 May nmod:tmod 3 15 May nummod 15 May flat 15 May 2015 15 May 2015 nmod:tmod nmod:tmod 4 15 May 2015 nummod nummod 15th May 2015 15th May 2015 nmod:tmod nmod:tmod 1 15th May 2015 compound nmod:tmod May 15 May 15 nmod:tmod 1 May 15 nummod May 15, 2015 May 15 , 2015 nmod:tmod nmod:tmod punct 5 May 15 , 2015 punct nummod May 15 , 2015 nmod:tmod punct nummod the 15th May 2015 AD the 15th May 2015 AD det nmod:tmodnmod:tmodnmod:tmod 1 the 15th May 2015 AD det amod nmod:npmod nummod the 15th of May the 15th of May det nmod:tmod case 4 the 15th of May det nmod case the 15th of May, 2015 the 15th of May , 2015 det nmod:tmod case nmod:tmod punct 3 the 15th of May , 2015 det nmod case nmod:tmod punct the 15th of May , 2015 det nmod case nummod punct B Survey of Czech Date Annotations in UD 2.8 B.1 CLTT Pattern Proposal Total CLTT Trees 15. kv\u011btna 2015 15. kv\u011btna 2015 amod:tmod nmod:tmod 12 15 . kv\u011btna 2015 nummod punct nummod k 15. kv\u011btnu kalend\u00e1\u0159n\u00edho roku k 15. kv\u011btnu kalend\u00e1\u0159n\u00edho roku case amod:tmod nmod:tmod amod 1 k 15 . kv\u011btnu kalend\u00e1\u0159n\u00edho roku case nummod punct nmod amod B.2 FicTree Pattern Proposal Total FicTree Trees 15. kv\u011btna 2015 15. kv\u011btna 2015 amod:tmod nmod:tmod 5 15 . kv\u011btna 2015 nummod punct nummod 15. kv\u011btna tohoto roku 15. kv\u011btna tohoto roku amod:tmod det 1 15 . kv\u011btna tohoto roku punct det B.3 PDT Pattern Proposal Total PDT Trees 15. 5. 2015 15. 5. 2015 nmod:tmod nmod:tmod 126 15 . 5 . 2015 compound punct compound punct 15. kv\u011btna 15. kv\u011btna amod:tmod 782 15 . kv\u011btna nummod punct 15 . kv\u011btna nummod:gov punct 15 . kv\u011btna obl punct 15. kv\u011btna l\u00e9ta P\u00e1n\u011b 2015 15. kv\u011btna l\u00e9ta P\u00e1n\u011b 2015 amod:tmod nmod:tmod nmod:tmod nmod 1 15 . kv\u011btna l\u00e9ta P\u00e1n\u011b 2015 nummod punct nmod nummod nmod 15. kv\u011btna roku 2015 15. kv\u011btna roku 2015 amod:tmod nmod:tmod nmod:tmod 1 15 . kv\u011btna roku 2015 nummod punct nmod nummod 15. kv\u011btna leto\u0161n\u00edho roku 15. kv\u011btna leto\u0161n\u00edho roku amod:tmod nmod:tmod amod 42 15 . kv\u011btna leto\u0161n\u00edho roku nummod punct nmod amod 15. kv\u011btna 2015 15. kv\u011btna 2015 amod:tmod nmod:tmod 240 15 . kv\u011btna 2015 nummod punct nummod B.4 PUD Pattern Proposal Total PUD Trees 15. kv\u011btna 15. kv\u011btna amod:tmod 8 15 . kv\u011btna nummod punct 15. kv\u011btna 2015 15. kv\u011btna 2015 amod:tmod nmod:tmod 10 15 . kv\u011btna 2015 nummod punct nummod 15. kv\u011btna 2015 p\u0159. n. l. 15. kv\u011btna 2015 p\u0159. n. l. amod:tmod nmod:tmod nmod:tmod case amod 1 nummod punct nummod case punct det punctpunct 15. toukokuuta 15. toukokuuta nmod:tmod 4 15. toukokuuta flat flat toukokuun 15. p\u00e4iv\u00e4n\u00e4 toukokuun 15. p\u00e4iv\u00e4n\u00e4 amod:tmod 1 toukokuun 15. p\u00e4iv\u00e4n\u00e4 flat nmod:tmod flat 15 Mei 2015 15 Mei 2015 153 nmod:tmod flat clf nmod:tmod nmod:tmod nummod nummod 15 Mei 2015 nmod:tmod nmod:tmod nmod nummod 15 Mei 15 Mei 4 15 Mei nmod nummod nummod 2015\u5e74\u4e94\u6708 2015 \u5e74 \u4e94 \u6708 2015 \u5e74 \u4e94 \u6708 1 2015 \u5e74 5 \u6708 15 \u65e5 nmod:tmod compound flat 15 . kv\u011btna 2015 p\u0159 . n . l . k 15. kv\u011btnu lo\u0148sk\u00e9ho roku k 15. kv\u011btnu lo\u0148sk\u00e9ho roku case amod:tmod nmod:tmod amod 1 k 15 . kv\u011btnu lo\u0148sk\u00e9ho roku case nummod punct nmod amod C Survey of Finnish Date Annotations in UD 2.8 C.1 FTB Pattern Proposal 15. toukokuuta 2015 15. toukokuuta 2015 nmod:tmod nmod:tmod 12 15. toukokuuta 2015 flat 15. toukokuuta 15. toukokuuta vuonna 2015 ekr. nmod:tmod nmod:tmodnmod:tmod nmod:tmod 1 15. toukokuuta vuonna 2015 ekr. flat flat toukokuun 15 p\u00e4iv\u00e4n\u00e4 2015 toukokuun 15 p\u00e4iv\u00e4n\u00e4 2015 nmod:tmod nmod:tmod 1 toukokuun 15 p\u00e4iv\u00e4n\u00e4 2015 flat flat nmod:tmod amod:tmod flat flat tanggal 15 Mei tanggal 15 Mei 9 nmod:tmod nmod:tmod flat clf nmod:tmod nmod:tmod nummod nummod tanggal 15 Mei flat nummod 15 Mei 2015 15 Mei 2015 15 Mei 2015 nummod clf nummod nmod 5\u670815\u65e5 5 \u6708 15 \u65e5 5 \u6708 15 \u65e5 6 6 nmod:tmod nmod:tmod acl:relcl nmod:tmod flat acl compound 2015 \u5e74 5 \u6708 15 \u65e5 compound tanggal 15 Mei clf nmod:tmod nmod:tmod nmod:tmod compound flat flat vuonna 2015 ekr. nmod:tmod flat toukokuun 15. p\u00e4iv\u00e4 toukokuun 15. p\u00e4iv\u00e4 1 toukokuun 15. p\u00e4iv\u00e4 nmod:tmod nmod:tmod amod:tmod flat flat flat tanggal 15 Mei compound 15 Mei tahun lalu 15 Mei tahun lalu 15 Mei tahun lalu clf case nmod:tmod nmod:tmod nmod:tmod case:loc nummod nummod nummod 1 nummod nmod pada tanggal 15 Mei pada tanggal 15 Mei case nmod:tmod nmod:tmod pada tanggal 15 Mei case nummod flat nummod nummod nmod:tmod \u516c\u5143\u524d2015\u5e745\u670815\u65e5 \u516c\u5143 \u524d 2015 \u5e74 5 \u6708 15 \u65e5 \u516c\u5143 \u524d 2015 \u5e74 5 \u6708 15 \u65e5 1 2015 \u5e74 5 \u6708 15 \u65e5 compound 4 case nmod nmod:tmod nmod:tmod compound nmod:tmod flat Total FTB Trees 15.5.2015 15. 5. 2015 nmod:tmod nmod:tmod 10 15.5.2015 15. toukokuuta 15. toukokuuta nmod:tmod 15 toukokuuta 15 toukokuuta nmod:tmod 1 15 toukokuuta nummod toukokuun 15. toukokuun 15. nmod:tmod 1 toukokuun 15. toukokuussa 2015 toukokuussa 2015 nmod:tmod 4 C.2 OOD Pattern Proposal Total OOD Trees 15.5.2015 15. 5. 2015 nmod:tmod nmod:tmod 18 15.5.2015 15. toukokuuta 15. toukokuuta nmod:tmod 3 15. toukokuuta flat 15. toukokuuta 2015 15. toukokuuta 2015 nmod:tmod nmod:tmod 3 15. toukokuuta 2015 flat flat C.3 PUD C.4 TDT Pattern Proposal Total TDT Trees 15.5.2015 15. 5. 2015 nmod:tmod nmod:tmod 23 15.5.2015 15 p\u00e4iv\u00e4n\u00e4 toukokuuta 2015 15 p\u00e4iv\u00e4n\u00e4 toukokuuta 2015 nmod:tmod nmod:tmod nmod:tmod 120 15. toukokuuta 15. toukokuuta nmod:tmod 47 15. toukokuuta flat 15. toukokuuta 2015 15. toukokuuta 2015 nmod:tmod nmod:tmod 185 15 Mei 15 Mei 22 15 Mei D.3 PUD 2015 \u5e74 5 \u6708 15 \u65e5 2015\u5e745\u670815\u65e5 2015 \u5e74 5 \u6708 15 \u65e5 12 2015 \u5e74 5 \u6708 15 \u65e5 15. toukokuuta 2015 flat flat tanggal 15 Mei 2015 tanggal 15 Mei 2015 D.2 GSD Pattern Proposal nmod:tmod nummod tanggal 15 Mei 2015 yang lalu tanggal 15 Mei 2015 yang lalu nmod nmod nmod:tmod 1 tanggal 15 Mei 2015 yang lalu nmod:tmod nmod:tmod nmod:tmod nummod nummod nummod nmod Total GSD Trees tanggal 15 Mei 2015 lalu tanggal 15 Mei 2015 lalu 1 acl:relcl nmod:tmod nmod:tmod nmod:tmod nsubj nmod nummod amod nummod nmod:tmod nmod:tmod compound nmod nsubj 2015\u5e745\u670815\u65e5 2015 \u5e74 5 \u6708 15 \u65e5 264 compound 2015 \u5e74 5 \u6708 15 \u65e5 2015\u5e745\u6708 2015 \u5e74 5 \u6708 14 2015 \u5e74 5 \u6708 tanggal 15 Mei 2015 lalu nmod:tmod nmod:tmod nmod:tmod nummod nummod nummod 5 tanggal 15 Mei 2015 tanggal 15 Mei 2015 nmod:tmod nmod:tmod nmod:tmod nummod nmod:tmod nmod:tmod nmod:tmod nmod:tmod nummod nummod clf nummod 15 p\u00e4iv\u00e4n\u00e4 toukokuuta 2015 flat flat flat 15 Mei 2015 15 Mei 2015 nmod:tmod nmod:tmod 32 15 Mei 2015 nummod nummod 15 Mei 2015 flat 15 Mei lalu 15 Mei lalu acl:relcl nmod:tmod 5 15 Mei lalu nummod acl:relcl nmod:tmod nmod:tmod nmod:tmod nummod nmod:tmod nummod nmod:tmod nummodnummod tanggal 15 Mei 2015 obl nummod nummod tanggal 15 Mei pada tahun itu tanggal 15 Mei pada tahun itu nmod:tmod nmod:tmod nmod:tmod case det 1 tanggal 15 Mei pada tahun itu nmod nmod nummod case det acl:relcl nmod nmod:tmod compound clf amod 2015 \u5e74 5 \u6708 nmod:tmod nmod:tmod nmod:tmod 141 2015 \u5e74 5 \u6708 nummod clf nummod 2015 \u5e74 5 \u6708 nmod nmod nummod \u540c\u5e74 5 \u6708 nmod:tmod nummod E.2 PUD Pattern Proposal Total PUD Trees E 2015\u5e745\u6708 \u540c\u5e745\u6708 \u540c\u5e74 5 \u6708 21 \u540c\u5e74 5 \u6708 \u540c\u5e74 5 \u6708 toukokuussa 2015 nummod toukokuussa 2015 toukokuussa 2015 nmod:tmod 15 toukokuussa 2015 nummod 15 Mei 15 Mei nmod:tmod 12 flat tanggal 15 Mei 2015 tanggal 15 Mei 2015 SM tanggal 15 Mei 2015 SM 1 nmod:tmod nummod nummod tanggal 15 Mei 2015 SM 15 Mei nummod acl nmod:tmod nmod det nummod nummod nmod:tmod nmod:tmod nmod:tmod nmod:tmod nummod flat nmod \u4e94\u6708\u5341\u4e94\u65e5 \u4e94 \u6708 \u5341\u4e94 \u65e5 1 \u4e94 \u6708 \u5341\u4e94 \u65e5 flat nmod toukokuun 15. p\u00e4iv\u00e4n\u00e4 toukokuun 15. p\u00e4iv\u00e4n\u00e4 vuonna 2015 amod:tmod nmod:tmod vuonna 2015 Pattern Proposal Total CSUI Trees tanggal 15 Mei 2015 tanggal 15 Mei 2015 nmod:tmod nmod:tmod nummod nummod 1 toukokuun 15. p\u00e4iv\u00e4n\u00e4 vuonna 2015 flat D Survey of Indonesian Date Annotations in UD 2.8 D.1 CSUI compound nmod:tmod clf nummod nummod nmod flat flat 5\u670815\u65e5 5 \u6708 15 \u65e5 67 5 \u6708 15 \u65e5 12 15. toukokuuta amod toukokuun 15. p\u00e4iv\u00e4 toukokuun 15. p\u00e4iv\u00e4 amod:tmod 1 toukokuun 15. p\u00e4iv\u00e4 flat nmod:tmod nmod:tmod flat flat tanggal 15 Mei 2015 tanggal 15 Mei 2015 tanggal 15 Mei 2015 5 nmod:tmod nmod:tmod nummod nummod tanggal 15 Mei 2015 flat toukokuun 15. p\u00e4iv\u00e4 2015 toukokuun 15. p\u00e4iv\u00e4 2015 2 toukokuussa 2015 toukokuussa 2015 nmod:tmod 50 nummod nummod nmod:tmod clf toukokuussa 2015 nummod tanggal 15 Mei 2015 tanggal 15 Mei 2015 100 tanggal 15 Mei 2015 flat pada tanggal 15 Mei nmod:tmod nmod:tmod nmod:tmod nummod flat flat 2015 \u5e74 5 \u6708 15 \u65e5 nummod nummod \u53bb\u5e745\u670815\u65e5 \u53bb\u5e74 5 \u6708 15 \u65e5 1 \u53bb\u5e74 5 \u6708 15 \u65e5 nummod toukokuun 15. p\u00e4iv\u00e4 2015 nmod:tmod nmod:tmod nmod:tmod nummod nummod nmod nmod:tmod nmod:tmod nummod nummod
", "type_str": "table", "text": "", "num": null } } } }