EVENTI Annotation Guidelines for Italian Technical Report v. 1.0 Tommaso Caselli+ and Rachele Sprugnoli∗ TrentoRISE+ FBK-HLT∗ and Univeristy of Trento∗ Via Sommarive, 18 Povo (TN) IT-38123 [email protected] [email protected]

July 29, 2014

Contents 1 Introduction

3

2 Events in TimeML 3 2.1 Event extents . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.1.1 Verbs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.1.2 Nouns . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 2.1.3 Prepositional Phrases . . . . . . . . . . . . . . . . . . . 11 2.1.4 Adjective . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.1.5 Multi-Token Events: Collocations, Idioms, Named Events, Constructions Involving “esserci” and Modal Periphrasis “in grado di” . . . . . . . . . . . . . . . . . . . . . . 13 2.2 Event attributes . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.2.1 class . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.2.2 part-of-speech . . . . . . . . . . . . . . . . . . . . . 20 2.2.3 tense, aspect, mood, vform . . . . . . . . . . . . . . . 20 2.2.4 modality . . . . . . . . . . . . . . . . . . . . . . . . . 23 3 Temporal Expressions 23 3.1 TIMEX3: tag span . . . . . . . . . . . . . . . . . . . . . . . . 25

1

3.2

3.3 3.4

3.1.1 Grammatical Criteria . . . . . . . . . . . . . . . 3.1.2 Relational Criteria . . . . . . . . . . . . . . . . 3.1.3 What NOT to tag . . . . . . . . . . . . . . . . TIMEX3 normalization: filling the attributes . . . . . . 3.2.1 Temporal Expression ID: tid . . . . . . . . . . 3.2.2 Temporal anchor time ID: anchorTimeID . . . . 3.2.3 Begin and end points: beginPoint endPoint . 3.2.4 Classifying temporal expressions: attribute type 3.2.5 Annotation of value: expressing the meaning of poral expressions . . . . . . . . . . . . . . . . . 3.2.6 Function in document: functionInDocument . 3.2.7 met`a : when it influences the value attributes . Empty TIMEX3 tags . . . . . . . . . . . . . . . . . . . Annotation rules . . . . . . . . . . . . . . . . . . . . .

4 Signals

. . . . . . . . . . . . . . . . . . . . . . . . tem. . . . . . . . . . . . . . .

. . . . . . . .

25 32 33 34 34 34 35 35

. . . . .

36 44 45 45 48 51

5 TLINKs 52 5.1 Rules for TLINK Directionality . . . . . . . . . . . . . . . . . . 52 5.2 The relType Attribute . . . . . . . . . . . . . . . . . . . . . . 53 5.2.1 Assigning the Value to the relType Attribute . . . . . 53 5.2.2 Clarifications on the SIMULTANEOUS, IBEFORE, IAFTER and IDENTITY values . . . . . . . . . . . . . . . . . . . 55 5.3 The SignalID attribute . . . . . . . . . . . . . . . . . . . . . 58 5.4 Subtasks for the Annotation of TLINKs . . . . . . . . . . . . . 58 5.4.1 TLINKs between Events in the Same Sentence . . . . . 58 5.4.1.1 TLINKs between Events in an identity relation . . . . . . . . . . . . . . . . . . . . . . 59 5.4.1.2 Identification of Main Events at the clause level 59 5.4.1.3 TLINKs between Main Events in the Same Sentence . . . . . . . . . . . . . . . . . . . . . 61 5.4.1.4 TLINKs between Main Event and Subordinated Event in the Same Sentence . . . . . . 61 5.4.1.5 TLINKs between Events in predicate-complement relation . . . . . . . . . . . . . . . . . . . . . 68 5.4.2 TLINKs between Events and Timexes in the Same Sentence . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 5.4.2.1 Events realized by nouns, adjectives and PPs 69 5.4.2.2 Events realized by verbs . . . . . . . . . . . . 69 5.4.2.3 relType Values for TLINK between an Event and a Timex . . . . . . . . . . . . . . . . . . 70 2

1

Introduction

This document reports the annotation guidelines employed for annotating the Italian data set for the EVENTI Tasks1 (both main and pilot) for the EVALITA 20142 Evaluation Campaign. The annotation is in accordance with the TimeML scheme and its adaptation to Italian under the ISO TC37 / SC4 initiatives (Pustejovsky et al., 2003; ISO, 2008). The overall annotation process will be split in two sequential subtask: first identify the relevant markables in the text, and then characterize them with the appropriate attributes or links. The structure of this document will reflect this division.

2

Events in TimeML

The term “event” is used as a cover term for all words denoting a situation which happens, occur, hold, take place. In literature this notion is often referred to as eventuality (Bach, 1986). An event can be durative or punctual. Predicates which describe states or circumstances which hold or are true are considered instances of events as well. The EVENT tag is also used to annotate states, but only a subsets of states are annotated, that is transient states or those which explicitly participates in a temporal relations. Thus, for instance in “Marco ` e alto” (Mark is tall) no annotation will be performed, since the state of being tall is not transient nor participates explicitly to a temporal relations. On the other hand, “Marco ` e uno studente” (Mark is a student) is to be considered as possible markable. Syntactically, the linguistic elements which may realize an event are the following (markable expressions are in bold): (a) Verbs (finite or non-finite form) e.g.: • I pompieri hanno isolato la sala. [The fire brigade isolated the room.] (b) Predicative constructions e.g. : • Al Sayed ` e il nuovo presidente della Fermenta. [Al Sayed is the new president of Fermenta.] 1 2

https://sites.google.com/site/eventievalita2014/ http://www.evalita.it/2014

3

• Un centinaio di giovani ` e tuttora agli arresti. [A hundred young people are still in custody.] (c) Nouns, which can realize eventualities in three different ways (Gross & Kiefer, 1995): • deverbal nouns, obtained through a nominalization process from verbs; e.g.: fuga [escape], arrivo [arrival], corsa [run], bevuta [drink], accordo [agreement]. . . ; • nouns which are not derived from a verb and have an eventive meaning in their lexical properties; e.g.: guerra [war], uragano [hurricane], assemblea [meeting], cerimonia [cerimony]. . . ; • nouns which normally denote objects but which are assigned an eventive reading either through the process of type-coercion, or through the processes of logical metonymy and coercion induced by temporal prepositions (Pustejovsky, 1995); (the co-textual elements which give rise to the type-coercion phenomenon are underlined) e.g.: – Ho interrotto il libro. [I’ve interrupted my book.]

2.1

Event extents

In this section we will present the guidelines specification used for the annotation of events in the Italian data of the EVENTI competition. The notion of minimal chunk developed in TimeML will apply in most cases. Exceptions to this notion which allow for multi-token events will be signaled in the dedicated section 2.1.5. 2.1.1

Verbs

All verbal predicates, including those denoting states, are considered as instances of events and hence will be marked up as such. The following specifications guidelines applies: • Finite and non-finite verb forms: annotate only the verbal head. Auxiliaries are not annotated. Clitics can be included in the verb form as the annotation is on token level: (1) I pompieri hanno isolato la sala. [The firebrigade isolated the room.] 4

hanno isolato (2) La riunione sta per chiudersi [The meeting is about to end.] chiudersi (3) Il PIL Italiano non `e cresciuto nell’ultimo trimestre. [The Italian GDP did not grow in the last quarter.] • Modal verbs (volere, dovere, potere) + verbs: annotate both the modal verb and the main verb (at the infinitive): (4) L’assemblea deve prendere una decisione. [The assembly must take a decision.] deve prendere (5) Non ho potuto chiamare l’ufficio. [I couldn’t call the office.] ho potuto chiamare • Copular constructions: annotate both the copular verb and its argument: (6) L’assemblea `e stata solidale con loro. [The meeting was in solidarity with them.] e ` stata solidale (7) L’assemblea `e sembrata sfiancata dalla lunga discussione. [The assembly looked exhausted by to the long discussion.] e ` sembrata sfiancata • Modal periphrases which code modality not realized by proper modal verbs (see also Section 2.1.5): (8) A oggi siamo in grado di dire che l’accordo non `e stato raggiunto. (Modal periphrasis) [As of today we are not able to state that an agreement has been reached.] siamo in grado di dire 5

(9) C’`e da dire che questo trattamento non `e soddisfacente. (Modal periphrasis) [We have to say that this treatment is not satisfying.] C’ e ` da dire • Aspectual constructions: annotate the verb and its argument with two separate tags. The argument of these constructions are always eventive. (10) Il magistrato ha iniziato a condurre le indagini sulla morte di Calipari.(Phasal/Aspectual periphrasis) [The attorney started its investigations on the death of Calipari.] ha iniziato a condurre • Constructions involving light verbs: we have considered as eligible light verbs in Italian the following verbs: FARE, DARE, METTERE + NOUN/eventive PP and AVERE + eventive NOUN. In case the construction involving one of this verb is NOT contained in the list of multi-tokens events (see Section 2.1.5), then mark the verb and the nominal/prepositional complement with two separate eventive tags. For prepositional complements the general rules for the annotation of events realized by PPs apply (see section 2.1.3). The two elements will be linked by means of a TLINK: identity. Some examples on light verb constructions are reported in Appendix 5.4.2.3 (11) fare una domanda. [ask a question.] fare una domanda (12) avere bisogno. [to be in need.] avere bisogno (13) dare peso. lit. [give weight.] dare peso

6

• causative constructions involving “fare + INFINITIVE” [make + INFINITIVE]: mark both elements with two separate tags. Note that in these cases, the class value of the verb “fare” will always be OCCURRENCE. Variability in class assignment apply only to the complement verb according to the It-TimeML specifications for the class attribute. (14) I pompieri hanno fatto evacuare la sala. lit. [The fire-brigade make evacuate the room.] hanno fatto evacuare • special cases: what follows is a list of special cases in which both elements (verb and noun) are to be marked: ` — FATTURATO — GUADAGNO — i. light verb + ATTIVITA INTROITO — INCASSO — ONERI — PERDITA — PROF` — UTILE . . . ITTO — REDDITIVITA ii. REGISTRARE + FATTURATO — GUADAGNO — INTROITO `— — INCASSO — PERDITA — PROFITTO — REDDITIVITA UTILE — PROFITTO — VANTAGGIO . . . + numeric expression (amount): annotate both the verb and the noun; do not annotate the numeric expression; iii. RAGGIUNGERE + FATTURATO — GUADAGNO — INTROITO `— — INCASSO — PERDITA — PROFITTO — REDDITIVITA UTILE — PROFITTO — VANTAGGIO . . . + numeric expression (amount): annotate both the verb and the noun; do not annotate the numeric expression; iv. FATTURATO — GUADAGNO — INTROITO — INCASSO — ` — UTILE — PROFPERDITA — PROFITTO — REDDITIVITA ITTO — VANTAGGIO . . . + AMMONTARE + A numeric expression (amount): annotate both the noun and the verb; do not annotate the numeric expression; 2.1.2

Nouns

Only the noun head is to be annotated. Determiners and modifiers are excluded. Exceptions to the minimal chunk rule are given in Section 2.1.5. Nouns are always to be annotated with an event tag in the following cases: • the noun denotes an event:

7

(15) embargo [embargo], guerra [war], pace [peace], attacco [attack]. . . • the noun is a named event, such as “Guerra Mondiale”: please note that for this type of nouns the minimal chunk rule does not apply (see Section 2.1.5 for details); • the noun is a complement of an aspectual event; • the noun denotes a cause or an effect, or is a complement of a causative predicate and does not refer to a human entity3 ; (16) Il fuoco ha distrutto il bosco [The fire destroyed the forest.] fuoco ha distrutto (17) Le piogge hanno causato la frana. [The rains caused the landslide.] piogge hanno causato la frana • the noun is a complement of an inchoative predicate expressing a change of state,: (18) Presto diventeranno dottori di ricerca. [They will soon become Ph.Ds.] diventeranno dottori (19) Marco sar`a presidente dell’ENI. [Marco will be the president of ENI.] sar` a presidente • the noun is a complement of a copular verb; 3

In sentences like “Marco ha causato un incendio” of the type ENTITY causee1 EVENTe2 the causal expression (e1) and its event complement (e2) are both tagged as independent events but the entity is not to be annotated.

8

• the noun denotes a sortal state (presidente [president], dottore [doctor], . . . ) and it co-occurs with temporal modifiers such as ex [ex/former], nuovo [new], prossimo [next] . . . or it functions as the head of a predicative complement4 . (20) L’ex presidente della Fiat 5 . [The former FIAT president.] presidente • it is a deverbal noun with an eventive reading; • it denotes a set of actions; • it is followed by a post-modifier which denotes a temporal expression: (21) il bilancio del 1991. [the balance of 1991]. bilancio del 1991 (22) L’assemblea dei lavoratori di ieri. lit. [the meeting of the workers of yesterday.] assemblea dei lavoratori di ieri Special rules apply for complex nominal construction of the kind “NOUN + DI [of] + NOUN” . The following guidelines apply: • NOUN event + DI + NOUN event: mark both nouns; e.g.: (23) il finanziamento della ristrutturazione. [the funding of the renovation.] il finanziamento della ristrutturazione • NOUN event + DI + NOUN notEvent: do not annotate the non eventive noun; e.g.: 4

A predicative complement expresses a predication and is the complement of a verb belonging to one of the following classes, among others: copulative predicates, inchoative predicates, aspectual predicates, change of state predicates. 5 Please note that “ex” is annotated as a TIMEX3.

9

(24) attacco di panico. [panic attack.] attacco di panico • NOUN notEvent + DI + NOUN event + DI + NOUN notEvent: annotate the eventive noun; (25) i diritti di sfruttamento delle riserve idriche. [the rights of exploitation of water resources.] i diritti di sfruttamento delle riserve idriche • NOUN event + DI + NOUN event + DI + NOUN event + DI + NOUN event—notEvent: annotate all the eventive nouns; e.g.: (26) Il fallimento del progetto di ristrutturazione della casa. [the failing of the project of renovation of the house.] il fallimento del progetto di ristrutturazione della casa A further class of nouns which can be annotated is represented by the class of functional nouns. Functional nouns are nouns like temperatura [temperature], popolazione [population], taglia [size], utile [profit], intensit`a [magnitude], aumento [increase], crescita [growth] . . . They take an individual as their argument and return a value on a scale, which can be numeric or not (e.g. high, low, big . . . ). With respect to TimeML, in It-TimeML and for the EVENTI task, we have adopted a restrictive notion of functional nouns by annotating only functional nouns which have a clear eventive reading. This means that functional nouns such as temperatura [temperature], popolazione [population], taglia [size], intensit`a [magnitude] are never annotated. The following special cases have been elaborated by keeping into account the specific TimeML class (see Section 2.2.1 for details) to which the first noun of such a construction can belong to. • NOUN reporting + DI + NOUN; e.g.: (27) La dichiarazione del fallimento. . .

10

la dichiarazione del fallmento • NOUN aspectual + DI + NOUN (28) La fine della partita la fine della partita • NOUN perception + DI + NOUN (29) La vista dello schianto la vista dello schianto (30) La vista di Mario la vista di Mario • Nominalizations of performative verbs + DI + NOUN (31) L’ordine di sgombero l’ ordine di sgombero 2.1.3

Prepositional Phrases

Prepositional phrases are considered as instances of events only when in copular constructions. Only the head of the PP is to be marked. In case the prepositional phrase gives rise to a collocation, then multi-token event annotation rules apply (see section 2.1.5) (32) I passeggeri erano a bordo del volo Oceanic 815. [Passengers were on board of flight Oceanic 815.] i passeggeri erano a bordo del volo... Notice that the head preposition (or the multi-token prepositional phrase) is marked as eventive only if the verb, noun or adjective within the PP does not denote an event itself 11

(33) Senza persare se ne and`o. [Without thinking, he left.] senza pensare (34) Lo show `e iniziato con un’intervista al presidente. [The show began with an interview to president.] con un’ intervista 2.1.4

Adjective

There are two types of adjectives: attributives and predicatives. Only adjectives in predicative positions are annotated as events. Notice that the property denoted by the adjective must be non-persistent and fit into one of the following cases: • the property the adjective denotes is clearly non-persistent, fluid; e.g. (35) Nick divent`o rosso per la vergogna. [Nick turn red with shame.] divent` o rosso per la vergogna • the property the adjective denotes is presented as temporally bounded to a particular point or period of time; e.g.: (36) Parte del nord Italia era sottosviluppato fino al XIX◦ secolo. [Part of North Italy was underdeveloped until XIX◦ secolo.] era sottosviluppato • the property the adjective denotes is presented as the opinion, knowledge, belief of somebody; e.g.: (37) Si ritiene furbo. [He consider himself clever.] ritiene furbo NOTE: in case of doubt adjectives have not been annotated. 12

2.1.5

Multi-Token Events: Collocations, Idioms, Named Events, Constructions Involving “esserci” and Modal Periphrasis “in grado di”

We identified a restricted set of specific cases where the minimal chunk rule can be “violated”, namely collocations and idiomatic expressions contained in reference resources6 . In this cases, the tag spans over the entire construction. In case the collocation or idiomatic expression is broken due to adverbial modification, then two separate tags must be created, as for light verb annotation, and connected by means of a TLINK: identity. (38) fare le valige. [to pack.] fare le valigie (39) Ho fatto gi`a le valige. [I’ve already packed.] Ho fatto gi` a le valigie As for events involving the lemma “esserci” (it is a verbo procomplementare corresponding to there + to be constructions in English), both the locative adverb “ci” and the verb “essere” are annotated in a single tag. (40) C’`e Marco. [There is Marco.] C’ ` e Marco. The modal periphrasis involving “in grado di” [able to/can] is annotated in a single tag. (41) Non sono in grado di venire. [I am not able to come.] 6

The full list is available at https://sites.google.com/site/eventievalita2014/ data-tools/poliremEVENTI.txt?attredirects=0&d=1

13

Non sono in grado di venire. As for named events, different types can be distinguished, for example: • names of shows, congresses and exhibitions should be annotated only when used as metomymic expressions; (42) ”Acque e Territorio” `e iniziato luned`ı. "Acque e Territorio" e ` iniziato • names of historical events should be annotated as multi-token expressions when they are entries of Wikipedia (43) Ha chiesto spiegazioni sulla strage di Beslan sulla strage di Beslan •

2.2

Event attributes

In the dataset distributed for the EVENTI task, the following 8 attributes associated to the tag will be available: 1. Class 2. Part-of-speech 3. Tense 4. Aspect 5. Polarity 6. Modality 7. Mood 8. Vform i.e. verb form

14

The attributes part-of-speech, tense, aspect, polarity, mood and vform are superficial attributes, that is that the assignment of their values is based on the surface form of the markable element. The attribute class on the other hand employs syntactic and semantic criteria based on the class definition. Please note that only the class attribute will be considered for evaluation in Task B. 2.2.1

class

The class attribute is assigned on the basis of an interaction between semantic and syntactic features. Each event is classified in one of the following TimeML classes: REPORTING, PERCEPTION, ASPECTUAL, I ACTION, I STATE, OCCURRENCE, STATE. • REPORTING: “Reporting events describe the action of a person or an organization declaring something, narrating an event, informing about an event, etc” (ISO (2008): 48); e.g.: dire, spiegare, raccontare, affermare, notizia, commento. . . (44) Punongbayan hadetto che dal vulcano fuoriuscivano gas con temperature fino a 1.800 gradi. (45) Citando l’esempio di. . . . • PERCEPTION: “Events involving the physical perception of another event” (ISO (2008): ibid.); e.g.: vedere, guardare, osservare, ascoltare, sentire,. . . (46) Dei testimoni hanno dichiarato alla polizia di aver delle persone fuggire. • ASPECTUAL: these events code information on a particular phase or aspect in the description of another event. They are a grammatical device which code a kind of temporal information and focus on different facets of the event history. They may signal one of the following aspects: (a.) Initiation: iniziare, incominciare. . . . (b.) Reinitiation: rincominciare. . . . (c.) Termination: smettere, terminare, cessare, interrompere. 15

(d.) Culmination: finire, completare. . . (e.) Continuation: continuare, andare avanti.. . . Some examples: (47) iniziando il consueto lancio di pietre. (48) una trattativa gi`a conclusaper l’acquisizione. • I ACTION: “I ACTION stands for intensional action. I ACTIONs describe an action or situation which introduces another event as its argument, which must be in the text explicitly”. (ISO (2008): 49). It is important to point out the difference between “intensional” and “intentional” or purposeful. I ACTIONs include but are broader than actions with intended consequences. Note that nouns, in particular nominalizations, can be classified as I ACTIONS as well. In the following examples, I ACTIONs are marked with the XML tag and their event arguments are underlined; e.g.: (a.) cercare, provare, tentare. . . (49) Compagnie come la Microsft stanno di monopolizzare. (b.) investigare, indagare, ricercare, progettare. . . (50) Una nuova task force ha inizato a indagare sull’uccisione di 14 donne. (51) `e ormai in fase avanzata il progetto di ricorrere al mercato. (c.) ritardare, postporre, ostacolare. . . (52) Israele chieder`a agli Stai Uniti di ritardare l’attacco contro l’Iraq. (d.) evitare, impedire, prevenire, cancellare, disdire. . . (53) La cancellazione dei voli dell’Alitalia ha creato disagi.

16

(54) La Questura di Livorno ha impedito lo svolgimento della manifestazione di Forza Nuova indetta per il 10 Febbraio. (e.) chiedere, ordinare, persuadere, comandare, richiedere, autorizzare (55) Le autorit`a hanno richiesto la massima collaborazione da parte dei mezzi di informazione. (f.) promettere, offrire, assicurare, proporre, accordarsi, decidere (g.) nominare, eleggere • I STATE: “They are similar to the events in the previous class because I STATEs also select for another event as their argument, but contrary to I ACTIONs, they denote stative situations” (ISO (2008): ibid.). The I STATEs are marked with the XML tag, whereas their embedded argument is underlined. Again, nouns can be classified as I STATEs.; e.g.: (a.) credere, pensare, immaginare, essere sicuro, sospettare. . . (56) Crediamo che le sue parole non abbiano distratto il pubblico da quello che `e accaduto. (b.) sembrare, desiderare, bramare, auspicare. . . (57) Il governo italiano ha auspicato un’intesa in tempi rapidi. (c.) sperare, aspirare. . . (58) Sperano che i residenti rientreranno nelle loro case una volta cessato l’allarme. (d.) temere, odiare, essere preoccupato, aver paura, spaventarsi. . . (59) Temevano per la loro incolumit`a. (e.) aver bisogno, necessitare. . . 17

(f.) dovere, potere, volere, sapere, essere in grado di, riuscire (60) I soldati devono essere ritirati dall’Iraq. • STATE: States describe circumstances in which something obtains or holds true. Some examples are: (61) Numerosi punk sono tutt’ora agli arresti. (62) auto e cabine telefoniche distrutte . (63) Una partecipazione garantita dalla presenza dei nostri ministri. (64) In totale, sono pi` u di 4 milioni gli stranieri regolari in Italia The class of STATE does not contain any instance of I STATEs which in case of absence of event argument are marked as OCCURRENCE. The only exceptions are related constructions involving the copulative verbs7 , such as “essere” [to be], “diventare” [to become], and “avere” [to have], which may alternate between STATE and I STATE. • OCCURRENCE: This class includes all other types of events describing situations that happen or occur in the world. (65) Il patrimonio dell’Assofondi `e cresciuto. (66) I ministri dei 150 Paesi se ne tornano in patria. (67) L’ uragano, definito di ” prima grandezza ” , `e in grado di provocare danni per miliardi di dollari. For the EVENTI data set, these rules for the class assignment apply: • the arguments which may influence the assignment of a class (i.e. the event arguments) can be: 7

http://www.treccani.it/enciclopedia/verbi-copulativi_(Enciclopedia_ dell’Italiano)/

18

– a direct object; – an indirect object; – a complement clause/sentence; – in passive contexts, the subject; • complement purpose clauses, causative relations and conditional constructions DO NOT influence the assignment of the class; • copular verb “essere” and eventive predicative argument: both elements have same class, namely STATE or I STATE. The class I STATE is assigned to modal/factive constructions such as “`e vero/falso/possibile/ consigliabile/chiaro/certo/... + che + CLAUSE” [it is true / false / possible / certain / clear / advisable that + CLAUSE], “`e consigliabile/... + EVENT” [It is advisable + EVENT] or “`e degno/capace/... + di + CLAUSE” [ worthy/able + of + CLAUSE]; • all modal verbs and modal periphrases have always class I STATE; • events realized by more than one token and annotated in two tags (e.g. light verb constructions) have the same class; • incremental nouns like calo, crescita, aumento, crollo, miglioramento, incremento and similar may vary class assuming as values either OCCURRENCE or STATE. The following heuristics apply: – when complements (both subject or object position) of verbs like segnare [to sign], conseguire [to reach], ottenere [to get], risultare [to result] and similar, they are STATE; – when followed by DI + NUMBER [of + NUMBER] constructions, they are STATE; – in all other cases, they are OCCURRENCE. • As a general rule, past participles have class STATE. However, if a past participle occurs in constructions of the kind “PAST PARTICIPLE + DA + ENTITYAGEN T ” [PAST PARTICIPLE + BY + ENTITYAGEN T ], the past particple has class OCCURRENCE; e.g.: (68) Le operazioni continuano protette e garantite dai consorzi. Le operazioni continuano avanti protette e 19

garantite dai consorzi. In case a past participle has an event as its argument (PAST PARTICIPLE + EVENT), the class of the past participle is assigned by following the general rules for class assignment. (69) impedita la manifestazione. impedita la manifestazione • an event is annotated as belonging to the class REPORTING if it is the translation equivalent of one of the lexical units assigned to the Communication frame in FrameNet, which has Message as a core element. Among the frames using and inherited from the Communication frame, only the ones having the Message as a core element and conveying a giving information speech act have been selected and the lexical units belonging to them have been classified as Reporting Events: e.g. urlare [to scream] from the Communication noise frame, sottolineare [to stress] from the Convey importance frame, dichiarare [to declare] from the Statement frame. 2.2.2

part-of-speech

It signals the distinction of the different grammatical categories which may realize an event. Its values are VERB, for events realized by verbs or VPs, ADJECTIVE, for events realized by adjectives, NOUN, for events realized by nouns, PREPOSITION, for events realized by prepositional phrases. Multi-tokens events have the part of speech as the head of the collocation or idiomatic expressions. (70) fare le valigie. fare le valigie

2.2.3

tense, aspect, mood, vform

The tense and aspect attributes capture standard distinctions among grammatical categories of verbal phrases. The assignment of the value is based on the superficial form according to these criteria: 20

• superficial grammatical form of simple finite verbs; • superficial grammatical form of the main auxiliary verb for composed finite verb forms; The vform and mood attributes capture the distinctions between finite and non-finite verb forms and between different modalities of the event realization respectively. What follows are the values to be assigned for tense, aspect, mood and vform attributes: 1. Events realized by finite verb forms (active and passive voice): • tense= “PRESENT” vform=“NONE” -

gioca aspect= IMPERFECTIVE mood= NONE sta giocando aspect= PROGRESSIVE mood= NONE ha mangiato aspect= PERFECTIVE mood= NONE ´e mangiato aspect = IMPERFECTIVE mood= NONE (che) mangi aspect= IMPERFECTIVE mood = SUBJUNCTIVE

• tense= “PAST” vform=“NONE” - gioc`o aspect= PERFECTIVE mood= NONE - ebbe l’abitudine di giocare aspect= PERFECTIVE mood= NONE - fu mangiato aspect= PERFECTIVE mood= NONE - `e stato mangiato aspect= PERFECTIVE mood= NONE - (che) abbia mangiato aspect= PERFECTIVE mood = SUBJUNCTIVE - aveva giocato aspect= PERFECTIVE mood= NONE - ebbe giocato aspect= PERFECTIVE mood= NONE - era stata mangiata aspect= PERFECTIVE mood= NONE - (che) avesse mangiato aspect= PERFECTIVE mood = SUBJUNCTIVE - giocava aspect= IMPERFECTIVE mood= NONE - stava giocando aspect= PROGRESSIVE mood= NONE - aveva l’abitudine di giocare aspect= IMPERFECTIVE mood= NONE - era mangiata aspect= IMPERFECTIVE mood= NONE

21

- (che) mangiasse aspect= IMPERFECTIVE mood = SUBJUNCTIVE • tense= “FUTURE” vform= “NONE” -

giocher`a aspect= PERFECTIVE mood= NONE avr`a giocato aspect= PERFECTIVE mood= NONE sar`a mangiata aspect= PERFECTIVE mood= NONE star`a mangiado aspect=PROGRESSIVE mood= NONE

• tense= ”NONE” - mangerebbe aspect= IMPERFECTIVE mood= CONDITIONAL - sarebbe mangiato aspect= IMPERFECTIVE mood= CONDITIONAL - avrebbe mangiato aspect= PERFECTIVE mood= CONDITIONAL - sarebbe stato mangiato aspect= PERFECTIVE mood= CONDITIONAL - starebbe mangiando aspect= PROGRESSIVE mood= CONDITIONAL • tense= “NONE” vform=“NONE” - mangia aspect= NONE mood= IMPERATIVE 2. Events realized by non-finite verb forms: • tense= “NONE” vform=“’INFINITIVE” mood= “NONE” - giocare aspect= NONE - aver giocato aspect= PERFECTIVE - stare giocando aspect= PROGRESSIVE • tense= “NONE” vform=“GERUND” mood= “NONE” - giocando aspect= NONE - avendo giocato aspect= PERFECTIVE • tense= “NONE” vform=’“PARTICIPLE” mood= “NONE” - giocante aspect= NONE - giocato aspect= PERFECTIVE 3. Events realized by adjectives, nouns or prepositional phrases: • tense= “NONE” • aspect= “NONE” 22

• vform= “NONE” • mood= “NONE” In case of predicative clauses, the copular verb assumes values for tense, aspect, mood and vform as described for finite verb forms whereas nouns, adjectives and prepositional phrases have always value ”NONE”. 2.2.4

modality

The annotation of the attribute modality is done only when a modal verb or a modal periphrases is present. The value of the modality attribute corresponds to the lemma of the modal verb or of the modal periphrasis.

3

Temporal Expressions

What is normally referred to with the label temporal expressions (i.e. timexes) in the NLP community is only a small and closed subset of words which have temporal reference or meaning. In particular, as it is stated in the annotation guidelines of TIDES (2001) “the flagging of temporal expressions is restricted to those temporal expressions which contained a reserved time word, called lexical trigger” (Ferro et al. (2001). This means that many other words (e.g. scuola, presidenza, incubazione . . . ) which can assume a temporal reading are excluded. The specifics of the TimeML tagset for annotating temporal expressions differ from both the TIMEX tag in STAG and the TIMEX2 tag in TIDES, though some common points are kept. With respect to the tag, tag does not allow nested tags, has a larger set of attributes to capture the timex meaning (normalization) and it does not allow temporal prepositions (i.e. contracted prepositions in Italian) as part of tag extension. The tag marks up any temporal expression referring to: (a.) Day times (mezzogiorno, 3, la sera, la mattina . . . ); (b.) Dates of different granularity: days (ieri, 8 Gennaio 1980, venerd`ı scorso, sabato . . . ), weeks (la prossima settimana, la seconda settimana del mese . . . ), months (tra due mesi, il mese prossimo, l’ Agosto del 1980 . . . ), seasons or business quarters (la scorsa primavera, lo scorso semestre, il primo trimestre, il bimestre . . . ), years (1980, l’anno scorso, . . . ), centuries, . . . 23

(c.) Durations (due mesi, cinque ore, nei prossimi anni, il periodo . . . ). (d.) Sets (una volta al mese, ogni marted`ı . . . ). The linguistic realizations (parts-of-speech) of temporal expressions present a reduced set of variations with respect to the eventualities and are, in a certain way, more regular. In Table 1 we report some of the possible linguistic realizations of temporal expressions together with some examples. Table 1: Temporal expression triggers and corresponding POS. Timex Lexical Triggers agosto, alba, anniversario, domenica, estate, giornata, serata, futuro, lustro, stagione. . . Natale, Pasqua, Capodanno, Ferragosto 25/07/2007, 1980, 13:11. . . annuale, primaverile, estivo, mensile. . . annualmente, oggi, ora, allora, adesso, finora, ieri, tutt’ora. . . primo, secondo, 1, 31, 28. . .

POS

Nouns Proper Nouns Calendar/Time Patterns Adjectives Adverbs Numbers

Additional properties of timexes related to their meaning are: • Granularity level: the value of a timex may be more or less precise. An expression like “lo scorso fine settimana” can refer to the entire week-end or a specific day in the week-end. The timeline format used to normalize the values of timexes, i.e. to assign them a standard value corresponding to point (or interval) on a calendar/clock or to an unanchored duration, is based on the Gregorian calendar, and derived from the ISO 8601 standard for time values. The format is of the general form YYYY-MM-[WW]DDhh:mm:ss.This means that the granularity of an expression can have the values Year, Month, Week, Day, Hour, Minute and Second including also Millennium (M ), Century (C ), and Decades (D). • Fuzziness: many timexes have fuzzy boundaries in their intended values with respect to when the denoted time period starts and ends, e.g.; ora, circa tre anni, nei primi anni sessanta . . . • Ambiguity: like many other expressions, timexes can be ambiguous, e.g. the expression “il prossimo mese” if uttered on July 25th, 2007, can 24

mean August 2007, or exactly one month after the moment of utterance, i.e. August 25th 2007. Disambiguating a timex means figuring out which of the possible values is the intended one. In the remaining of this section, only the attributes relevant to the EVENTI task are described. Please note that in task A only type and value attributes will be evaluated but the other attributes are important for a complete normalization of the timex. 1. type 2. value 3. anchorTimeID 4. beginPoint 5. endPoint 6. functionInDocument

3.1

TIMEX3: tag span

The surface-oriented approach to the tagging of expressions in ISO-TimeML implies that temporal expression annotation is based on the constituent structure: the time unit classification is presented in Table 2. Table 2: Time units classification. t
3.1.1

month≤t≤year t >year estate lustro semestre secolo anno biennio 1984 Febbraio

Grammatical Criteria

The span of the tag must correspond to one of the following categories: • Noun Phrase: luned`ı, mese, la scorsa estate. . . 25

• Adjectival Phrase annuale, estivo, mensile, quotidiano. . . • Adverbial Phrase oggi, ieri, finora. . . • Time/Date Patterns: 31-12-2006, 14.30, 24/08 . . . Definite and indefinite articles are to be included in the tag span. On the contrary, all prepositions, including contracted prepositions, and subordinating conjunctions introducing a temporal expression are not to be considered part of the timex tag. This is due to the fact that relevant temporal prepositions, and other signals of temporal relations, are marked with the SIGNAL tag (see Section 4 : (71) nel pomeriggio. nel pomeriggio (72) per l’autunno. per l’autunno Exceptions are represented by the prepositions “circa”, “intorno a” and “verso” which must be included into the extent of the tag because they have a role in the normalization of the timex: (73) per circa un mese. per circa un mese (74) verso le 10 di sera. verso le 10 di sera Further exceptions are represented by multiwords like per ora, dopo domani, fin’ora, di recente and similar where the whole expression is considered as a single unit and so the preposition is included into the tag: (75) per ora.

26

per ora (76) dopo domani. dopo domani (77) fin’ora. fin’ora (78) poco fa. poco fa All pre- and post-modifiers of a temporal expression must be included into the tag, with the exception of postmodifiers denoting an event: (79) durante lo scorso trimestre. durante lo scorso trimestre (80) il mese scorso. il mese scorso (81) nel secondo semestre. nel secondo semestre (82) tre giorni fa. tre giorni fa (83) il giorno della partenza. il giorno della partenza (84) appena tre giorni fa. 27

appena tre giorni fa The word “dopo” must be included into the tag span only when it has the function of adjective, otherwise it is to be excluded: (85) dopo tre giorni. dopo tre giorni (86) tre giorni dopo. tre giorni dopo If the postmodifier is realized by one of the following items, i.e. “esaminato”, “in esame”, “in analisi”, “analizzato”, “preso in esame”, “ considerato”, “a questa parte”, “in corso” and similar, the postmodifier has to be included into the timex extent since it is essential for its normalization. Relative clauses realized as “che rimane / che rimangono” (i.e. “rimanente/i ”) and “che segue / che seguono” (i.e. “seguente/i ”) are to be included into the TIMEX3 tag extent. If a temporal trigger word is preceeded by the expression “ci`o/quel che resta/rimane + di/del + timex trigger” it is to be included into the TIMEX3 tag. Further modifiers (both in premodifier position and postmodifier position) to be included into the TIMEX3 tag to ease normalization are “in/di ritardo” (i.e. “dopo”) and “in/di anticipo” (i.e. “prima”). Appositives are considered as postmodifiers, and thus are included into the tag span. However, if the appositive contains a lexical trigger for timexes we have two separate expressions: (87) gli anni ’60, gli anni del libero amore. gli anni ’60 gli anni del libero amore Conjoined temporal expressions can be marked either in two separate tags or in a single one. The following rules apply: • if the two temporal expressions refer to two independent points or intervals of time, then two distinct tags must be created; 28

(88) nel 2005 e nel 2006. nel 2005 e nel 2006 (89) 6 o 7 giorni. 6 o 7 giorni • if the two temporal expressions denote a clock time, then a single tag must be created; (90) alle 13 e 56. alle 13 e 56 • if the temporal expressions denote durations and the conjunction is expressing a specification relation between the temporal expressions, then one single tag must be created; (91) 3 anni, 6 mesi e un giorno. 3 anni, 6 mesi e un giorno Two consecutive temporal expressions are marked up into a single tag when they belong to the same syntactic constituent and specify a unique time value, otherwise two different tags must be created: (92) la mattina del 20 giugno la mattina del 20 giugno (93) ottobre del 1963 ottobre del 1963 (94) alle 11 di ieri mattina alle 11 di ieri mattina 29

(95) i primi mesi dell’anno i primi mesi dell’anno (96) il primo trimestre dell’anno il primo trimestre dell’anno (97) venerd`ı sera alle 20.00. venerd` ı sera alle 20.00 (98) ieri alle 11.00. ieri alle 11.00 (99) due settimane a ottobre due settimane a ottobre Temporal expressions like “i primi 5 giorni della settimana” do not express a unique temporal value but two, notwithstanding the presence of the preposition “della” and the fact that the temporal expression belong to the same syntactic constituent (i.e. a complex NP; see section 3.1.2 point (ii.) for further details). (100) i primi 5 giorni della settimana i primi 5 giorni della settimana We accept the extensions proposed in Lavelli et al. (2005) to be marked into a single TIMEX3 tag: 30

(101) ore e ore. ore e ore (102) di giorno in giorno. di giorno in giorno (103) giorno dopo giorno. giorno dopo giorno (104) 24 ore su 24. 24 ore su 24 (105) anno dopo anno. anno dopo anno Further extentions are the following: (106) al momento. al momento (107) per il momento. per il momento (108) poco fa. poco fa Temporal expressions which differs from the standard Gregorian calendar are to be annotated as illustrated below: (109) l’anno scolastico 2008/2009. l’anno scolastico 2008/2009 (110) l’anno fiscale ’92 - ’93. l’anno fiscale ’92 - ’93 The adjectives and adverbs in Table 3 are instances of temporal expression trigger words and thus must be annotated. Notice that the tokens “presente/passato/futuro” are considered as instances of temporal expressions only when they are adjectives or complement of a PP. In case they are nouns, they are never marked up as temporal expressions. 31

Table 3: Special adjectival and adverbial triggers. Token ex, recente, attuale corrente passato, presente, futuro recentemente, di recente, attualmente

3.1.2

POS Adjective Adjective Adverb

Relational Criteria

According to the type of relation which exists between two consecutive temporal expressions, different rules apply for the tag span. In these cases: • A single tag must be created: (i.) the two expressions belong to the same temporal unit, as illustrated in Table 2 on page 25, or they are hierarchically related: (111) venerd`ı sera. venerd` ı sera (112) venerd`ı ore 11. venerd` ı ore 11 (113) marted`ı 26 giugno marted` ı 26 giugno (114) giugno 1969. giugno 1969 • Two tags must be created: (i.) when two temporal expressions are in an anchoring relation: (115) venerd`ı sera alle 20.00. venerd` ı sera alle 20.00 (116) due settimane da oggi due settimane da oggi (117) tre giorni prima di ieri 32

tre giorni prima di ieri (118) il terremoto `e avvenuto un anno fa oggi. il terremoto e ` avvenuto un anno fa oggi (ii.) when they give rise to framed durations: the temporal expression contains a date (in bold) and a duration (underlined). In these cases two tags are created together with two empty tags (see Subsection 3.3 for fully annotated examples of framed durations). (119) i primi 6 mesi dell’anno i primi 6 mesi dell’ anno (120) i primi dieci anni del XX◦ secolo i primi dieci anni del XX◦ secolo le due ultime settimane del mese le ultime due settimane del mese 3.1.3

What NOT to tag

Among non markable time expressions, together with those expressions which can have a temporal meaning but are not considered trigger words, we include (all non markable elements are in bold): • Frequency expressions, when no time period is given: (121) L’ Italia `e diventata campione del mondo per quattro volte. (122) I gestori si sono mostrati spesso inclini alla cautela. • Sequencing and ordering expressions: (123) Le perizie erano state inizialmente predisposte dal presidente. • Manner adverbs: 33

(124) La vendita sar`a annunciata a Roma e a Londra contemporaneamente. (125) Subito soccorsa dai medici presenti nel villaggio. • Non-quantifiable durations: (126) Un investimento da liquidare a breve termine. (127) Attendevano da tempo lo sblocco delle certificazioni. • Proper names that contain or correspond to lexical triggers but denote something other than a temporal entity (e.g., films, books, organizations): (128) Settembre Nero. (129) Domani aprir`a la mostra “Il secolo breve”. (130) “1984” `e un libro di George Orwell.

3.2

TIMEX3 normalization: filling the attributes

The tag has a large set of attributes. In the EVENTI task A only type and value attributes will be evaluated. Anyway, in the rest of this subsection, all the attributes are described and annotated examples given. 3.2.1

Temporal Expression ID: tid

It assigns a unique ID number to each timex instance. It is automatically assigned by the annotation tool whenever the tag is assigned to a string. 3.2.2

Temporal anchor time ID: anchorTimeID

This attributes introduces the id value of the temporal expression to which the TIMEX3-marked expression is linked in order to compute its value. To illustrate how this attribute works, consider the following example: (131) Ieri circa mille giovani hanno lasciato la citt`a. “Ieri ” requires the application of a temporal function: to know the calendar date corresponding to “Ieri ” we need to identify its temporal anchor, that is another temporal expression which helps us to recover all the necessary 34

information to identify its Year, Month and Day. Imagine this anchor is the time at which the document has been created, whose id is t0, then we will obtain this representation: (132) Ieri circa mille giovani hanno lasciato la citt`a. 3.2.3

Begin and end points: beginPoint endPoint

These attributes are used to strengthen the annotation of durations. They are used when a duration is anchored to one or two temporal expressions which signal(s) its beginning and/or ending point(s) (See type=‘‘DURATION’’ in Section 3.2.4).

3.2.4

Classifying temporal expressions: attribute type

The attribute type specifies the type of the timex. Its values are DATE, TIME, DURATION and SET. • DATE: this type applies to all temporal expressions which describe a calendar time. (133) 1,6 milioni di sterline di utile nel 1985 . (134) Ha sostanzialmente contestato l’accordo raggiunto venerd`ı scorso. • TIME: the temporal expression refers to a time of the day, even if in a very indefinite way. Clock times are classified as TIME as well. (135) L’ ultima ondata di violenza si `e scatenata sabato notte. (136) L’assemblea `e iniziata alle 15.00 . • DURATION: the expression describes a duration, i.e. a period of time not pointing to any specif area in the time axis. This value is assigned only to explicit durations. (137) La trattativa dura ormai da oltre un mese. 35

(138) Un incremento del 105 per cento in 10 mesi . As a rule, if any specific calendar information is supplied in the temporal expression, then the type of the TIMEX3 must be either DATE or TIME. For instance, an expression like “1985” cannot be marked as a DURATION, even if the context may suggest that an event holds throughout that year. Temporal expressions like the former “must always be of type DATE, since they refer to a particular area in the temporal axis –even though that area spans over a period of time” (ISO (2008): 57). • SET: The expression describes reoccurring time expressions. (139) Meno di un milione di tonnellate all’anno. (140) un raduno che dal 1982 si tiene quasi tutti gli anni . 3.2.5

Annotation of value: expressing the meaning of temporal expressions

The value attribute expresses the meaning of a temporal expression. Its annotation is strictly dependent to the type value assigned to the temporal expressions. As a general rule, all temporal expressions should be given the following ISO 8601 format for dates: YYYY-MM-[WW]-DDThh:mm:ss, that is Year, Month, Week (optional), Day, Hour, Minute and Second 8 . However, natural language temporal expressions cannot always be reconducted to such forms, so some extensions have been introduced. A. DATE: they must always be reconducted to the format YYYY-MM-[WW]-DD: (141) venerd`ı due dicembre 2008. venerd` ı due dicembre 2008 (142) 07/08/1995 8

Some websites provide an interface to automatically calculate the week number: see, for example, the ISO week day calendar at http://www.personal.ecu.edu/mccartyr/ isowdcal.html or http://www.tuxgraphics.org/toolbox/calendar.html

36

07/08/1995 The annotator will introduce as much information as is available both in the time expression itself and in the context. In case the text would include some reference to the specific date in which the time is anchored, the annotator has to resolve it and assign the most specific value. Assuming that all the temporal expressions in the following examples have as anchor the date “venerd`ı 28 Novembre 2008 ”, we will obtain: (143) il 3 aprile prossimo. il 3 aprile prossimo (144) lo scorso 15 maggio lo scorso 15 maggio (145) ieri ieri (146) il 25/12 il 25/12 Weeks are assigned the position of Months in the date format and their value corresponds to the week number in the calendar of the corresponding year: W01 refers to the first week of the year and W53 to the last one. (147) questa settimana (referring to the week from 24-30 November 2008)

37

questa settimana If some information cannot be recovered from the context, then the missing information must be signaled using the placeholders X (148) il 1980 il 1980 (149) ad agosto ad agosto Temporal expressions which differs from the standard Gregorian calendar are to be normalized as follows (see also (Ferro et al., 2002) and (Lavelli et al., 2005)): • they are considered DATE; • in presence of the modifier “fiscale” [fiscal] they will always receive a normalize value by exploiting the symbol FY: (150) l’anno fiscale 2008 l’anno fiscale 2008 l’anno fiscale ’92 - ’93 l’anno fiscale ’92 - ’93 • in presence of modifiers other than “fiscale” [fiscal], they will remain underspecified for the normalized value: 38

(151) l’anno scolastico 2008/2009 l’anno scolastico 2008/2009 la stagione calcistica ’92 - ’93 la stagione calcistica ’92 - ’93 Please note that the last two examples are cases of culturally-determined expressions that are temporal expressions which interpretation requires cultural or domain-specific knowledge. This is the case also of holiday names like Natale. A holiday name is markable but should receive a value only when that value can be inferred from the context of the text, rather than from cultural and world knowledge. Otherwise the XXXX-XX-XX placeholder should be used. Following the extension proposed in the adaptation of TIDES to Italian, Table 4 presents some markable expressions which are classified as DATE together with their values representing an extension of standard ISO format: Notice that the symbols for “semestre” (H), “trimestre” (Q), “quadrimestre” (Qu) and “bimestre” (B) always co-occur with ordinal numbers from 1 up to a maximum of 6, and corresponds to the cardinal modifiers “primo”, “secondo” etc.. Thus, “il terzo trimestre” will receive value= XXXX-Q3, “il secondo semestre” will have value="XXXX-H2" and so on for the others. These four temporal expressions are assigned value DATE if and only if they co-occur with the cardinal modifiers because they denote a fixed set of months, e.g. “il terzo trimestre” corresponds to the months of “luglio - agosto - settembre”. If they do not co-occur with these modifiers or they refer to different set of months, then they are followed by an X. (152) il trimestre febbraio - aprile il trimestre febbraio marzo Fuzzy dates referring to the past (e.g. ex, passato), the present (e.g. oggigiorno, al momento) and the future (e.g. domani as a generic reference) are normalized using the values PAST REF, PRESENT REF, and 39

Table 4: Special DATE markables and value. Temporal Expression al momento, in questi giorni, tuttora, per ora, il/nel presente, a oggi, adesso recentemente, in/il passato, tempo fa, giorni fa poco fa il/al futuro, in futuro, il domani (generic reference), tra qualche mese/giorno/anno autunno, autunnale primavera, primaverile estate, estivo inverno, invernale fine settimana, week-end semestre trimestre quadrimestre bimestre

value

Annotation sample

PRESENT REF value="PRESENT REF"

PAST REF

value="PAST REF"

FUTURE REF FA SP SU WI WE H Q Qu B

value="FUTURE REF" value="XXXX-FA" value="XXXX-SP" value="XXXX-SU" value="XXXX-WI" value="XXXX-XX-WE" value="XXXX-H1" value="XXXX-Q1" value="XXXX-Qu1" value="XXXX-B1"

FUTURE REF respectively. Please note that the same lexical expression can have a fuzzy interpretation in a sentence (see the annotation of oggi in in the first example below where it has the “nowadays” meaning) and a precise interpretation in another sentence (see the annotation of oggi in the second example below).

(153) oggi ci sono moltissimi canali satellitari in TV oggi ci sono moltissimi canali satellitari in TV (154) oggi si insedia il nuovo Parlamento (DCT = 2008-12-02 tid=“t0”) 40

oggi si insedia il nuovo Parlamento B. TIME: all temporal expressions which correspond to the value TIME will begin with a ‘T’ (Time). The format is THH:MM:SS, that is Hours, Minutes and Seconds. If minutes and/or seconds are not specified the alternative formats are THH:MM and THH. The value are assigned on a 24 hour base (e.g. 4 p.m. = 16:00). (155) le 16.00. le 16.00 In case the text would include some reference to a specific date in which the time is anchored, then the date must be contained in the value attribute: (156) ieri alle 16.00 ieri alle 16.00 As for DATE, TIME presents some extensions as well. In Table 5, we present some trigger expressions which are classified as TIME but whose values cannot be reconducted to the standard ISO representation, namely THH:MM:SS: C. DURATION: these temporal expressions denote intervals. All durations’ value begins with a ‘P’ (Period of time). If the interval denoted by the duration can be determined by reasoning due to the presence of a beginning and an ending point, or if it is explicitly stated in the expression, then it is represented by an ordinal number; otherwise the placeholder X must be employed. In case of inferred durations non-text consuming TIMEX3 tags must be created to express the duration (see Section 3.3). The granularity value (Year, Month, . . . ) of the duration must always be expressed: 41

Table 5: Special TIME markables and value. Temporal Expression value Annotation sample mattina MO value="XXXX-XX-XXTMO" mezzogiorno, mezzod`ı MI value="XXXX-XX-XXTMI" pomeriggio AF value="XXXX-XX-XXTAF" sera, serata EV value="XXXX-XX-XXTEV" notte, nottata NI value="XXXX-XX-XXTNI" giorno (day time or working hours) DT value="XXXX-XX-XXTDT"

(157) 4 mesi 4 mesi (158) per 45 minuti. per 45 minuti (159) alcuni anni fa alcuni anni fa Date and time elements including their designator may be omitted if their value is zero and decimal fraction can be used. (160) due anni, un mese, tre giorni, 4 ore, cinque minuti e 59 secondi due anni, un mese, tre giorni, 4 ore, cinque minuti e 59 secondi (161) un mese 42

un mese (162) un minuto un minuto (163) mezza giornata mezza giornata Tokens are to be used to represent durations referring to periods of the day (MO, MI, AF, EV, NI, DT), weekends (WE), seasons (SP, SU, FA, WI), quarters (Q), year halves (H), and fiscal years (FY). (164) 3 notti 3 notti The placeholder X must be employed if the interval denoted by the duration cannot be determined by reasoning due to the presence of beginning and ending points, or if it is not explicitly stated in the expression. (165) alcuni anni alcuni anni D. SET: To fully annotate sets, the TIMEX3 must also include either the quant or freq attributes, if not both. The following examples present the annotation of TIMEX3 SET for the value attribute (please note that the annotation of quant and freq is not tackled as not relevant for the EVENTI task): 43

(166) una volta a settimana. una volta a settimana . (167) ogni tre giorni. ogni tre giorni (168) 3 giorni a settimana. 3 giorni a settimana (169) ogni ottobre. ogni ottobre Please note that in the last example, the value looks like a point and not a duration: in this way it’s possible to mark the calendar information (i.e. ottobre) present in the temporal expression. The general rule, useful to understand when to use a DATE-like annotation instead of a DURATIONlike format, is that if there is no specified calendar date (for example, ottobre or luned`ı), then the value for the SET will be like that of a DURATION. 3.2.6

Function in document: functionInDocument

This attribute indicates what is the function of a temporal expression in the document and its function as a temporal anchor for other temporal expressions. Its values are: (a.) CREATION TIME: the time the text is created; (b.) MODIFICATION TIME: the time the text is modified; (c.) PUBLICATION TIME: the time the text is published; 44

(d.) RELEASE TIME: the time it may be released (if not immediately); (e.) RECEPTION TIME: the time it is received by a reader; (f.) EXPIRATION TIME: the time that the text expires (if any) (g.) NONE: the default value; a general time without a particular reference to document ’s life. According to the annotated document, the Document Creation Time (DCT) can correspond either to the “CREATION TIME” or to the “PUBLICATION TIME”. 3.2.7

met` a : when it influences the value attributes

The modifier “met`a ” may vary its role on the basis of (i.) the granularity of the temporal expressions which modifies and (ii) the co-occurrence with ordinal adjectives such as “prima” and “seconda”. In Table 6 we illustrate in details how to normalize timexes with this modifier: Table 6: Values of the modifier met`a. Timex Sample met`a anno met`a giornata prima met`a dell’anno seconda met`a della settimana prima met`a del mese seconda met`a del giorno prima met`a del trimestre

3.3

Granularity Y TOD Y W M TOD M

Annotation val="YYYY" val="XXXX-XX-XXTDT" val="XXXX-H1" val="XXXX-WX" val="XXXX-XX" val="XXXX-XX-XXTDT" val="XXXX-QX"

Empty TIMEX3 tags

It-TimeML allows the creation of empty, non-text consuming TIMEX3 tags whenever a temporal expressions can be inferred from a text-consuming one. • Anchored durations contain a typical duration expression but refer in fact to a point in time (i.e. a date or time of day). They are so called because the duration is explicitly or implicitly anchored to a further temporal reference, that is an anchor.

45

– Anchored durations with implicit anchoring reference: the anchoring element is interpreted from the context. In this case a non-text consuming tag will be created referring to the implicit anchoring date. (170) un mese fa. (DCT = 2008-12-02 tid=“t0”) un mese fa (171) alcuni mesi fa. (DCT = 2008-12-02 tid=“t0”) alcuni mesi fa (172) ha svolto il suo mandato meno di un decennio fa e oggi si `e ritirato a vita privata. (DCT = 2008-12-02 tid=“t0”) meno di un decennio fa e oggi – Anchored durations with explicit anchoring reference: the anchoring element is present in the text, two annotations are possible depending on whether the point in time the duration refers to is a date or a time of day. ∗ If the resulting temporal expression refers to a DATE, 3 temporal expressions are annotated: i) the duration (underlined), ii) the date encoding the explicit anchoring reference (in bold), iii) the empty TIMEX3 encoding the resulting date of the full construction. (173) il terremoto `e avvenuto un anno fa oggi. (DCT = 2008-12-02 tid=“t0”) 46

il terremoto e ` avvenuto un anno fa oggi ∗ If the resulting temporal expression refers to a TIME of day: a single TIMEX3 tag of type “time” is annotated. (174) Arriv`o a 10 minuti alle 3 10 minuti alle 3 • Range expressions: range expressions involve two temporal expressions either of type DATE or of type TIME, which denote the begin and end points of an implicit duration. In this case a non-text consuming TIMEX3 tag expressing the duration must be created: (175) Marco (oggi) `e stato in palestra dalle 2 alle 5. (DCT = 2008-12-02 tid=“t0”) dalle 2 alle 5 • Framed durations: duration expressions that locate (or frame) a duration within the scope of a temporal unit which has a precise reference in the calendar. Differently to range expressions that denote time intervals using two temporal expressions of type DATE, framed durations denote a time interval and contain a DATE and a DURATION. The date refers to a particular temporal frame within which the duration is located, i.e. it expresses one of the boundaries of the interval. In case 47

of framed durations, two empty tags of type DATE will be created to express the begin and end points from which the length of the duration is computed. (176) i primi 6 mesi dell’anno (DCT = 2008-12-02 tid=“t0”) i primi 6 mesi dell’ anno (177) una settimana dopo il 10 luglio. (DCT = 2008-12-02 tid=“t0”) una settimana dopo il 10 luglio

3.4

Annotation rules

The following rules have been developed for the EVENTI dataset and apply when annotating temporal expressions: • Anchor identification: the anchor corresponds to the DCT, unless i.) there is a temporal expression in the document which represents a new temporal focus to which following temporal expressions are referred to; ii.) a coreference relation holds between two temporal expressions, i.e. the two temporal expressions are the same but are encoded in the document by means of different words.

48

• Normalization of TIME temporal expressions: TIME temporal expressions may realize either point (i.e. hours) or interval (i.e. time of day) temporal expressions. In case of TIME point temporal expressions, the default value for the normalization is computed by referring to hours belonging to the day before the DCT, unless more specific information are available which collocates the point temporal expression either as part of the DCT or as part of a previously mentioned temporal expressions; • Missing information for the value attribute: the use of placeholders for missing information must be related to temporal expression granularity. For instance, if the granularity of the temporal expression is a D(ay), then all missing information up to the final granularity value must be present and fulfilled by means of placeholders. (178) i primi di ottobre gran = M i primi di ottobre (179) i primi anni ’90 gran = Y i primi anni ’90 • All temporal expressions are normalized with respect to CEST Time Zone. Only when specified, GMT Time Zone has to be put into the normalized value; e.g.: (180) alle 15:00 alle 15:00 (181) alle 15:00 Gmt alle 15:00 Gmt 49

If an alternative time zone reference is given together with the local time, each expression is tagged separately. (182) alle 06.45 locali, le 12.45 italiane alle 06:45 locali , le 12.45 italiane In this previous example, “-06” indicates that the local time is five hours behind the CEST Time Zone. • Attribute value: when possible, always prefer point (i.e. YYYY-MM-DD) normalization to duration (i.e. PXG) normalization; – trigger word oggi : alway assign the point value YYYY-MM-DD corresponding to the DCT, anchorTimeID=DCT; – trigger words oggigiorno, ora, adesso: always assign point value PRESENT REF, anchorTimeID=DCT; – trigger words trimestre, bimestre, quadrimestre: they have TYPE=DATE; when they do not correspond to a standard value (i.e. primo trimestre = gennaio, febbraio, marzo), assign corresponding standard symbol followed by X; e.g.: (183) il bimestre febbraio marzo il bimestre febbario marzo – trigger word anno fiscale, trimestre fiscale. . . : the normalized value must be preceeded by the symbol FY; e.g.: (184) il prossimo anno fiscale il prossimo anno fiscale – granularity level: always normalize the temporal expression with respect to its granularity (G); e.g.: (185) il prossimo mese DCT = 2009-11-11 G = M(onth) 50

il prossimo mese (186) la settimana scorsa DCT = 2009-11-11 G = W(eek) la settimana scorsa (187) gioved`ı DCT = 2009-11-11 G = D(ay)/D(ay)O(f)W(eek) gioved` ı • Normalization of durations realized by TIME temporal expressions: the normalization value is PTXG, where X stands for the numbers, if present, which specify the duration of the durative expression and G stands for the granularity of the TIME temporal expression; e.g. : DT (working day), NI (night), H (hours), M (minutes)...; • Normalization of the temporal expression “d’ora in avanti ”: type = DATE, val = FUTURE REF, anchor = DCT. • In the normalization of the empty TIMEX3 tags, always fulfill the attribute anchor with the ID value of the temporal expressions from which the empty tag is created (188) un mese fa. (DCT = 2008-12-02 tid=“t0”) un mese fa

4

Signals

Textual elements which make explicit a temporal relation between two elements are annotated with the tag. The range of linguistic expressions which are to be marked as events is restricted to:

51

• Temporal prepositions: prima [before], durante [during], all simple and complex prepositions followed by a temporal expression. . . ; • Temporal conjunctions: textitprima [before], quando [when], mentre [while] . . . ; • Temporal adverbs: intanto [meanwhile] . . . • Special characters: “-” and “/”, in temporal expressions denoting ranges (e.g. 26 - 28 Settembre 2006 ); Each signal will be marked with a unique ID which will be reported in the relevant TLINK. Only signals entering in a temporal relations will be marked in the trainig set of the EVENTI task. The tag will not be evaluated.

5

TLINKs

This section reports the specifications for the annotation of temporal relations (i.e. TLINKs) for the EVENTI task based on those developed for the It-TimeML (Caselli et al., 2011). The tag represents the temporal relationship holding between two events, two temporal expressions, or between an event and a temporal expression, and indicates how they are temporally related. This section is structured as follows. Section 5.1 lists the rules used during the manual annotation to decide which markable expression is the source or the target of a TLINK. These rules are reported for descriptive purposes. In the EVENTI task, the directionality of a TLINK is not an issue as the scorer is able to deal with reciprocal temporal relations. Section 5.2 describes the values of the reltype attribute. Finally, in Section 5.4, the annotation specifications used for creating the dataset for the EVENTI tasks C and D are described.

5.1

Rules for TLINK Directionality

There is only one strict rule about directionaliy: in TLINKs of type MEASURE the source is always the TIMEX3 and the target is the Event. Other rules have been followed during the annotation of TLINKs but are not strict for the purpose of the annotation: • Between TIMEX3s: a TLINK between two TIMEX3s is created following the linear order of the sentence;

52

• Between a TIMEX3 and an Event: the source is the Event and the target is the TIMEX3. The only exception is given by the TLINK of type MEASURE as explained above; • Between two Events: a TLINK between two Events is created following the linear order of the sentence.

5.2

The relType Attribute

The set of temporal relations available between two markable expressions in TimeML is expressed by the values of the attribute relType. The full list of values for the relType attribute is: BEFORE, AFTER, IBEFORE, IAFTER, INCLUDES, IS INCLUDED, MEASURE, SIMULTANEOUS, BEGINS, BEGUN BY, ENDS, ENDED BY, and IDENTITY. Among the 13 possible values, five of them are binary - one being the inverse of the other - namely: BEFORE and AFTER, INCLUDES and IS INCLUDED, BEGINS and BEGUN BY, ENDS and ENDED BY, IBEFORE and IAFTER. 5.2.1

Assigning the Value to the relType Attribute

The full list and description of TLINK relTypes is reported in this section. For all relTypes except MEASURE, each source and target element in the link can involve either an EVENT or a TIMEX3. For clarity’s sake, in the following examples we will present only the annotation of the relevant entities involved in the temporal relations. (a.) SIMULTANEOUS: the two events are judged as simultaneous if they happen at the same time, or if an event is perceived as happening at a moment (point or interval) in time (for more details see Section 5.2.2): (189) Fumo instancabilmente quando scrivo. - Source: Fumo - Target: scrivo (b.) BEFORE: an event (or temporal expression) is before an other: (190) Alcuni giovani hanno saccheggiato un grande magazzino di generi alimentari prima di lasciare la citt`a. - Source: saccheggiato - Target: lasciare 53

(c.) AFTER: the inverse of the preceding relation; - Source: lasciare - Target: saccheggiato (d.) IBEFORE - Immediately before: one event/time occurs immediately before the other (for more details see Section 5.2.2): (191) Nell’ impatto tutti i passeggeri a bordo sono morti . - Source: impatto - Target: morti (e.) IAFTER - Immediately after: the inverse of the preceding relation (for more details see Section 5.2.2); - Source: saccheggiato - Target: lasciare (f.) MEASURE: this value is used to connect a temporal expression of type DURATION and an event. Not all temporal expressions of type duration can participate in this link but only those which provide information on the duration of the related event (i.e. temporal expressions which answer to the question “how long does/did the event X last?”): (192) Marco insegna per un’ora il luned`ı. - Source: un’ora - Target: insegna (g.) INCLUDES: one entity includes the other9 : (193) Marco `e arrivato a Boston luned`ı. - Source: arrivato - Target: luned`ı (h.) IS INCLUDED: the inverse of the preceding relation; - Source: luned`ı - Target: textitarrivato (i.) BEGINS: one event/time marks the beginning of another event/time: 9

It corresponds to Allen (1984)’s during relation.

54

(194) Si cerca un accordo da ieri . - Source: ieri - Target: cerca (j.) BEGUN BY: the inverse of the preceding relation; - Source: cerca - Target: ieri (k.) ENDS: an event/time marks the ending of another event/time: (195) Marco ha studiato fino alle 7 . - Source: 7 - Target: studiato (l.) ENDED BY: the inverse of the preceding relation; - Source: studiato - Target: 7 (m.) IDENTITY: this value does not signal a real temporal relation. For details see Section 5.2.2. 5.2.2

Clarifications on the SIMULTANEOUS, IBEFORE, IAFTER and IDENTITY values

A. SIMULTANEOUS: it is assigned to two markables either when they are perceived as happening at the same time, or when they temporally overlap, or when they occur close enough that it is not possible to further distinguish their times. This value is to be assigned also to the event arguments of perceptions verbs when required and/or present (see example 197). On the contrary, it is not possible to have a SIMULTANEOUS relation between a DURATION and an EVENT. (196) Quando Wong Kwan ha speso 16 milioni di dollari per comprare la casa, pens`o che fosse un buon affare. speso ... 55

pens` o (197) Ho sentito esplodere la fabbrica, poi il silenzio. sentito ... esplodere (198) Marco `e arrivato a Pisa alle 3. arrivato ... 3 56

B. IBEFORE and IAFTER: these relations are specifications of the more general BEFORE and AFTER relations. Their annotation is subordinated to the presence of specific signals, like “subito dopo”, or other discourse elements which indicate that the temporal span between the two entities involved is very short: (199) E’ caduto subito dopo la aver vinto. relax ... subito dopo la respirazione C. IDENTITY: this value applies to the following constructions: • causative constructions of the kind “FARE + INFINITIVE” and “EVENT causare EVENT”; (200) La pioggia ha causato delle alluvioni. - Source: causato - Target: alluvioni - relType: identity (201) La polizia ha fatto evacuare la zona. - Source: fatto - Target: evacuare - relType: identity 57

• light verb constructions: the TLINK connects the two elements of the constructions, i.e. the verb of very light semantic content (e.g., avere, fare) and the nominal event acting as its selected complement. • copular constructions: the TLINK connects the two elements of the constructions, i.e. the the copular verb (e.g. essere, sembrare) and its event complement. Notice: at this level of annotation the use of the value identity does NOT apply to annotate event coreference.

5.3

The SignalID attribute

The signalID attribute is optional and corresponds to the ID of the SIGNAL which contributes to the identification of a temporal relation between two entities. This attribute will not be evaluated in Task C and Task D.

5.4

Subtasks for the Annotation of TLINKs

In order to simplify the explanation, in the following subsections the annotation procedure is divided into a set of subtasks. The complete set of temporal relations that will be evaluated in EVENTI can be obtained by merging the different subtasks. There are two main types of TLINKs: TLINKs between two events in the same sentence and TLINKs between an event and a temporal expression in the same sentence. Cross-sentence temporal relations are not covered by this annotation. Notice that what is written in brackets is considered a new sentence so no TLINKs are to be annotated between tags outsite and tags inside brackets. For example, in Marco `e arrivato (alle 12) prima della partenza di Carlo, there isn’t any TLINK between the event “arrivato” and the temporal expression “12”. 5.4.1

TLINKs between Events in the Same Sentence

Within the set of temporal relations between two events in the same sentence a distinction can be made:

58

1. TLINKs between events occurring in different clauses (verb-verb or noun-verb relations) 2. TLINKs between events in a predicate-complement relation (verb-noun relations) Concerning events in different clauses, two types of TLINKs have been annotated for the EVENTI task, namely: TLINKs between main events (Section 5.4.1.3 and TLINKs between a main event and a subordinated event (Section 5.4.1.4. Issues related to the identification of main events in It-TimeML are discussed in Section 5.4.1.2: please note that this identification is different from the one proposed in English TimeML. Concerning TLINKs between events in a predicate-complement relation, we have restricted the annotation to events occurring in a temporal complement (Section 5.4.1.5). What follows is a description concerning proper TLINKs relations. As for events standing in identity relations please refer to section 5.2.2. 5.4.1.1 TLINKs between Events in an identity relation TLINKs with value identity does not express a proper temporal relation. As illustred in section 5.2.2, this value is used in a restricted set of cases: causative constructions, light verb constructions and copular constructions. 5.4.1.2 Identification of Main Events at the clause level The main event in a sentence correspond to the ROOT element of the main (independent) clause of a sentence. A sentence can have more than one main event if it contains more than one independent clause joined by using punctuation or by using a coordinating conjunction (e.g. and )10 . The following rules apply: • in case the main event is realized by a light verb construction or by the copular verb “essere”, only the verb head must be considered as main event. • MODAL VERB + VERB: the main event is the VERB. • MODAL VERB + non verbalEVENT: the modal verb is the main event. • sembrare + VERB: sembrare is considered as the main event. 10

Please note that the identification of main events used in It-TimeML is different from the one described in English-TimeML for which there is only one main event per sentence.

59

• reporting events when introducing both a reported or a direct speech are to be considered as main events. • perception events are to be considered as main events. • non-verbal events can be considered as main events only when they are in NP sentences with no verbal element; e.g.: (202) questo il vero traguardo che dovr`a nel tempo raggiungere la Pierrel. questo il vero traguardo che dovr` a raggiungere la Pierrel. MAIN EVENT = traguardo • in coordination contexts there is a main event in each coordinate clause: in the sentence “Marco ha bussato ed `e entrato” [Marco knocked and got in] both bussato [knocked] and entrato [got in] are main events. • events in finite embedded clause marked with complementizer “che” or “di ” are NOT eligible to main events. • events introduced by subordinating conjunctions which give rise to hypothetical clauses (se), temporal clauses (quando, dopo, mentre, prima di ), concessive clauses (sebbene), purpose clauses (per, al fine di, perch´e, cosicch´e ), causative clauses (a causa di, per ), contrast clauses (rispetto a, mentre) and comparison clauses (come, simile a) are NOT eligible to main events. • events in relative clauses are NOT eligible to main events. • events in comparative contexts: the subordinated event is introduced by conjunctions like “come”, “pi` u di ”, “meno di ” and can NOT be considered as main event. • events in non-finite subordinate clauses (e.g. infinitive clauses or gerundive clauses) are NOT be considered as main events; e.g. (203) El Sayed ha invece minimizzato la presenza e l’importanza di De Nora sottolineando che la Dirtrust partecipa per solo il 9 per cento.

60

El Sayed ha inveceminimizzato la presenza e l’importanza di De Nora sottolineando che la Dirtrust partecipa per solo il 9 per cento. MAIN EVENT = minimizzato 5.4.1.3 TLINKs between Main Events in the Same Sentence A sentence can contain more than one main event only when it is made by different independent clauses joined by using punctuation or by using a coordinating conjunction. In determining the temporal relations between main events pay attention to the following elements: • if each of the main events is modified by a temporal expression, assign the temporal relations on the basis of the temporal relation which exists between the two temporal expressions; • if there is a signal connecting the two main events, assign the TLINK on the basis of the temporal relation which is coded by the signal; • tense (and viewpoint aspect) pairs may restrict the set of possible temporal relations. We illustrate these constraints in the Table reported in Appendix B. Notice that the temporal relations in that Table are reported according to the order of appearance of the tensed forms (i.e. from the first tensed event towards the second one). Moreover, since the complete set of relations between tense forms will give rise to 64 different tense combinations, we will go into the details only when more than one tense form is present into a temporal dimension (i.e. PRESENT PAST - FUTURE); • in some cases the correct interpretation of the TLINK is due to common sense and world knowledge: for example in the sentence “Marco ha bussato ed `e entrato” [Marco knocked and got in] the annotator knows that knocking on a door comes before entering the room even if there is no explicit signal (such as poi [then] in “Marco ha bussato e poi `e entrato” [Marco knocked and then he got in]). 5.4.1.4 TLINKs between Main Event and Subordinated Event in the Same Sentence The identification of the main event is based on the heuristics described in Section 5.4.1.2. The subordinated event is identified on the basis of syntactic relations of dependencies and it is restricted to 61

clausal realizations, either finite or non finite. In other words, the subordinated event is a verbal event. No TLINK is established in the following cases: • MODAL VERB (and modal periphrases) + VERB; • MAIN EVENT + SUB. FINAL CLAUSE; • events in relative clauses do not enter in a TLINK with the main event. A special rule applies for the verb “volere”: • VOLERE + INF = TLINK • VOLERE + CHE + finite clause = TLINK When the subordinate event is realized by a finite clause, the values of the TLINKs are established on the basis of the schema provided below. Notice that: (i.) the following schema provides the most likely values but it is not to be rigidly accepted; (ii.) in case there are temporal expressions or signals in the main or in the subordinated clause, use this information to order the events accordingly. • the main event is at the PRESENT (i.e. simultaneous with the DCT): – the subordinate clause is at the INDICATIVE mood: ∗ TLINK="simultaneous" = present tense (204) Somain che seisub stanco. TLINK="simultaneous" ∗ TLINK="after" = a PAST tense (205) Somain che sei statosub stanco. TLINK="after" ∗ TLINK="before" = a FUTURE tense (206) Somain che saraisub stanco. TLINK="before" – the subordinate clause is at the SUBJUNCTIVE mood: ∗ TLINK="simultaneous" = (subjunctive) present tense (207) Pensomain che siasub stanco. TLINK="simultaneous" ∗ TLINK="after" = (subjunctive) imperfective or past

62

(208) Credomain che sapessisub a cosa andavi incontro. TLINK="after" ∗ TLINK="before" = (subjunctive) present - with futurate reading (209) Credomain che (domani) vadasub al mare. TLINK="before" • the main event is at a tense of the PAST (i.e. before the DCT): – the subordinate clause is at the INDICATIVE mood: ∗ TLINK="simultaneous|is included" = imperfect (210) Ho saputomain che erisub stanco. TLINK="simultaneous" (211) Mi accorsimain che Maria telefonavasub . TLINK="is included" (212) Sebbene mi annoiassisub , sono rimastomain fino alla fine. TLINK="simultaneous" ∗ TLINK="after" = a PAST tense (213) Sapevomain che eri statosub malato. TLINK="after" (214) Le chiedevamain che cosa aveva vistosub . TLINK="after" (215) Mi hanno dettomain che hai vintosub . TLINK="after" ∗ TLINK="before" = present, simple future or imperfect (216) Mi ha promessomain che vasub al mare. TLINK="before" (217) Mi ha promessomain che andr`asub al mare. TLINK="before" (218) Ha promessomain che venivasub al mare. TLINK="before" – the subordinate clause is at the SUBJUNCTIVE mood: ∗ TLINK="after" = (subjunctive) imperfective or (subjunctive) past perfect (219) Credevomain che sapessisub a cosa andavi incontro. TLINK="after" (220) Carlo le chiesemain quanto lo avesse pagatosub . TLINK="after" 63

∗ TLINK="before" = (subjunctive) imperfect (221) Speravomain che arrivasisub . TLINK="before" – the subordinate clause is at the CONDITIONAL mood: ∗ TLINK="before" = (conditional) past (future-in-the-past) (222) Sapevomain che saresti arrivatosub . TLINK="before" (223) Le dissemain che non sarebbe pi` u tornatosub . TLINK="before" • the main event is at a tense of the FUTURE (i.e. after the DCT): – the subordinate clause is at the INDICATIVE mood: ∗ TLINK="simultaneous = present or simple future (224) Gli dir`omain che seisub stanco. TLINK="simultaneous" (225) Sbaglier`amain chi decider`asub di andarsene. TLINK="simultaneous" ∗ TLINK="after" = a PAST tense (226) Gli dir`omain che erisub malato. TLINK="after" (227) Le chieder`omain che cosa ha vistosub . TLINK="after" ∗ TLINK="before" = present (with futurate reading) or simple future (228) Mi prometter`amain che andr`asub al mare. TLINK="before" (229) Domani chiedomain dove andr`asub al mare. TLINK="before" When the subordinate event is realized by a non-finite clause (infinitive or gerundive), the values of the TLINKs are established on the basis of the following schemas. Notice that in these cases, the main verb tense form is NOT relevant for establishing the TLINK values, though it provides the textual temporal anchor for the subordinated non-finite event: • the subordinated event is at PAST INFINITIVE: – TLINK="after" 64

(230) Ha dettomain di aver vistosub Giovanni. • the subordinated event is at PAST GERUNDIVE: – TLINK="before" (231) Avendo vistosub Giovanni, ha lasciatomain la festa. Things are more complicated when the subordinated event is at SIMPLE INFINITIVE. As reported in Bertinetto (2003), the factors which contribute to the identification of the temporal relation between a main (finite) event and a subordinated event at simple infinitives are: (i.) the lexical semantics of the main verb; (ii.) the viewpoint aspectual value of the main verb, and (iii.) the lexical aspects of the main verb and the infinitive. The following schema describes the assignment of TLINK values: • Main verb is (i.) a volitional verb (desiderare, volere, bramare, ambire . . . ), or (ii.) a causative verb (causare, obbligare, proibire, promettere, semplificare, suggerire . . . ), or (iii.) a declarative/reporting verb (dire, narrare, certificare, rimproverare . . . ): – the lexical aspect of the simple infinitive is an event: ∗ TLINK="before" (232) Ha dettomain di andaresub via. (233) Ha proibitomain di correresub via. – the lexical aspect of the simple infinitive is a state: ∗ TLINK="is included" ` proibitomain restaresub . (234) E • Main verb is a perception event (corresponding to the TimeML class PERCEPTION): – TLINK="simultaneous" (235) Ha vistomain esploderesub l’aereo. • Main verb occurs in the construction VERBmain + A + SIMPLE INFINITIVE: – TLINK="simultaneous" (236) Rimasemain a guardaresub la TV l’aereo.

65

• Main verb is an epistemic verb of the kind (i.) pensare, credere, sospettare, ricordarsi . . . , or (ii.) sperare, temere . . . (TimeML class I STATE): – TLINK="simultaneous"; (237) Pensavamain di averesub ragione. (238) Credevamain di andaresub a lavoro. (239) Sper`omain di vinceresub la lotteria. • Main verb is a verb denoting intellectual perception (dimenticare, ricordare . . . ): – the lexical aspect of the simple infinitive is an event and the tense of the main event is Presente or Imperfetto: ∗ TLINK="simultaneous"; (240) Si ricordavamain di mangiaresub di tanto in tanto. – the lexical aspect of the simple infinitive is an event and the tense of the main event is Passato Prossimo, Trapassato Prossimo, Trapassato Remoto, Futuro (Semplice or Composto), or Passato Remoto: ∗ TLINK="before"; (241) Si ricord`omain di mangiaresub . (242) Si era ricordatomain di mangiaresub troppo tardi. – the lexical aspect of the simple infinitive is a state: ∗ TLINK="is included" (243) Si dimenticavamain di esseresub in ritardo. • Main verb is a verb denoting intellectual perception of the kind ritenere, accorgersi, constatare, percepire, osservare11 , scoprire . . . : – the lexical aspect of the simple infinitive is an event: ∗ TLINK="simultaneous"; (244) Notavamain di correresub poco. (245) Rimarcavamain di lavoraresub troppo. (246) Ritennemain di mangiaresub poco. 11

The sense of ”osservare” is to be interpreted as an intellectual activity such as ”rimarcare, notare, far presente” corresponding to the sense #1 in MultiWordNet.

66

– The lexical aspect of the simple infinitive is a state: ∗ TLINK="is included" (247) Not`omain di averesub caldo. (248) Ritennemain di averesub ragione. (249) Ritennemain di esseresub puntuale. In case the main verb is realized by a COPULA + ADJ or a COPULAR VERB (sembrare, apparire) + ADJ, then a TLINK must be created between the VERB and the simple infinitive. The following schema applies: • if the tense of the copula or the copular verb is at Presente or Imperfetto: – TLINK="simultaneous" | "before" with adjectives such as facile, difficile, brutto, bello, necessario, sufficiente, indispensabile, degno (di), costretto (a), impensabile, stanco (di), stufo (di) . . . . In this case the linguistic context is necessary in order to disambiguate. However, a preference for the simultaneous value is identified; (250) Eramain stanco di averesub ragione. [simultaneous] ` main difficile pensaresub che Marco parta. [simultaneous] (251) E • the tense of the copula or copular verb is Passato Prossimo, Trapassato Prossimo, Trapassato Remoto, Futuro (Semplice or Composto), or Passato Remoto: – TLINK="simultaneous"; (252) Fumain stanco di averesub ragione. (253) Sembr`omain difficile pensaresub che Marco partisse. • the adjective occurrs in a construction of the kind COPULA—COPULAR VERB + ADJ12 + A + SIMPLE INFINITIVE: – TLINK="before" (254) Eramain intenzionato a picchiaresub Giulio (255) Era statomain disponibile a lavoraresub per noi. In case the subordinated event is realized by a SIMPLE GERUND, the following schema applies: 12

The adjective denotes a psychological state involving an intentional aspect of the experincer (“statives + control”) (e.g. intenzionato a, incline a, interessato a, disposto a, prossimo a, avido di, ansioso di . . . )

67

• if the SIMPLE GERUND realize a manner adjunct: – TLINK="is includes"; (256) Siamo uscitimain correndosub . • if the SIMPLE GERUND realize an instrument adjunct: – TLINK="after"; (257) Non scegliendosub non ho potuto sceglieremain . • if the SIMPLE GERUND realize a temporal adjunct: – TLINK="simultaneous"; (258) Alzandosub gli occhi dal libro, ho vistomain la scena. – TLINK="before"; in this case, the simple gerund behave as a coordinated clause (though it is still a subordinated one). The whole sentence can be paraphrased as a coordination between two clauses with conjunction “e”: (259) Si sono barricatimain nella fabbrica, iniziandosub il lancio di pietre [Si sono barricatimain nella fabbrica e hanno iniziatosub il lancio di pietre]. 5.4.1.5 TLINKs between Events in predicate-complement relation This type of TLINKs focuses on temporal relations between verbs and nouns. As for the EVENTI task, we have restricted this type of relations to nominal events occurring in temporal complements of a verbal event. (260) Far`a le nomine all’assemblea. - Source: far` a - Target: assemblea - relType is included 5.4.2

TLINKs between Events and Timexes in the Same Sentence

The identification of the event which is linked to the temporal expression(s) is based on the following rules which differentiate according to the POS of the event or its context of occurrence.

68

5.4.2.1 Events realized by nouns, adjectives and PPs It is possible to identify a TLINK between a non-verbal event (a noun, an adjective or a PP) and a temporal expression when the temporal expression “modifies” the non-verbal event, namely: • the non-verbal event is modified by a temporal expression; (261) Il bilancioevent 1992timex . (262) L’extimex amministratoreevent delegato. (263) L’assembleaevent dei lavoratori di ieritimex . Specific heuristics have been developed for the following contexts: • constructions of the kind “A + TIMEX + DA + non verbalEVENT”: there is a temporal relation between the timex and the non-verbal event; (264) A 20 annitimex dalla chiusuraevent del monumento, la Torre riapre. • non-verbal event, temporal movement and extension verbs13 + TIMEX: there is a temporal relation between the non-verbal event and the timex. (265) L’assembleaevent slitta a domanitimex . 5.4.2.2 Events realized by verbs In case of events realized by verbs, the following rules apply: • if the timex is in the main clause, then there is a TLINK between the main verb of that clause and the timex; (266) Domanitimex il presidente si dimetter`aevent . • if the timex is in a subordinated clause, then there is a TLINK between the verb of the subordinated clause and the timex; (267) Il presidente ritiene che il decreto sar`a approvatoevent domanitimex . 13

We refer to verbs like “seguire”, “slittare”, “aggiornare”, “programmare”, “anticipare”, “rinviare”, “risalire” and similar.

69

• if a coordination relation stands between two or more verbs, then there is a TLINK between the timex and each verb in the coordination (at the same syntactic level); (268) Domanitimex il presidente dichiarer`amainevent di aumentaresubevent il fondo pensionistico e di ridurresubevent le tasse. TLINK = dichiarer` amainevent - domanitimex (269) Domanitimex il presidente dichiarer`amainevent di aumentaresubevent il fondo pensionistico e ridurr`asubevent le tasse. TLINK = aumentaresubevent - domanitimex TLINK = approvaresubevent - domanitimex • in case the timex is in the main clause and the subordinated clause is a temporal clause introduced by a signal (e.g. quando, allorch´e, (non) appena, una volta che, dopo (di/che), prima (di/che), come...), then there is a TLINK between the verb of the main clause and the timex and a TLINK between the verb of the subordinated temporal clause and the timex. (270) Oggitimex il presidente dichiarer`amainevent di aumentaresubevent il fondo pensionistico prima di approvaresubevent il decreto . TLINK = dichiarer` amainevent - Oggitimex relType="IS INCLUDED" TLINK = approvaremainevent - Oggitimex relType="IS INCLUDED" Notice: in case of events realized by more than one token (verb + nonverbal event) the TLINKs are marked up between the verbal element and the temporal expression. For construction like “MODAL VERB + VERB + TIMEX” and “ASPECTUAL VERB + VERB + TIMEX”, the TLINK is marked up between the verb and the timex and between the aspectual verb and the timex respectively. 5.4.2.3 relType Values for TLINK between an Event and a Timex This section describes a set of rules which have been developed in order to facilitate the agreement on the values of the relType attribute for TLINKs between an event and a timex in the same sentence. • in case no signal is present then the timex can identify either (i.) the temporal localizer of the event or (ii.) a textual temporal anchor. The 70

temporal localizer (in a broad sense) of the event provides the answer to the question “when does/did the event happen?” or “how long does/did the event last?”. The correct value is provided by the answer. Keep in mind that, with the exclusion of the value MEASURE, the TLINK directionality is from the event towards the timex; • the following TLINK values applies in presence of constructions of the kind “EVENT + SIGNAL + TIMEX”: – EVENT + per + DURATIONtype −→ relType=‘‘measure’’; (271) Marco ha corsoevent per 10 minutiduration . – EVENT + in/nel/nell’/nella/nei + DURATIONtype −→ relType=‘‘is included’’; (272) Nelle scorse settimaneduration hanno occupatoevent la stazione. – EVENT + in/nel/nell’/nella/nei + quantified DURATIONtype −→ relType=‘‘after’’; (273) In 5 minutiduration `e arrivatoevent al negozio. – EVENT + da/dalle/dal/dai/dall’ + DURATIONtype −→ relType=‘‘measure’’, if the event is a state; an additional TLINK with relType=‘‘begun by’’ is created between the EVENT and the beginning point of the duration (it can be a timex of type DATE in the text or an empty timex tag); (274) Da giorniduration hastate una strana camminata. – EVENT + da/dalle/dal/dai/dall’ + DURATIONtype −→ NO TLINK, if the event is an activity or a transition; a TLINK with relType=‘‘begun by’’ is created between the EVENT and the beginning point of the duration (it can be a timex of type DATE in the text or an empty timex tag); (275) Era venutatransition a Spoleto da qualche giornoduration . – EVENT + da/dalle/dal/dai/dall’ + DATEtype −→ relType=‘‘begun by’’; (276) Da ieridate dormeevent sul divano. (277) Da ieridate haevent una camminata strana. – EVENT + fino a/al/alle/all’/ai + DURATIONtype −→ NO TLINK; a TLINK with relType=‘‘ended by’’ is created 71

between the EVENT and the beginning point of the duration (it can be a timex of type DATE in the text or an empty timex tag); (278) Fino a tre anni faduration le segnalazioni eranotransition parecchie. – EVENT + tra + DURATIONtype −→ relType=‘‘after’’; (279) Consegnaevent il lavoro tra tre giornitimex . – EVENT + entro + DURATIONtype −→ NO TLINK; a TLINK with relType=‘‘ended by’’ is created between the EVENT and the ending point of the duration (it can be a timex of type DATE in the text or an empty timex tag); (280) Consegnaevent il lavoro entro tre giornitimex . – EVENT + entro + DATEtype −→ relType=‘‘ended by’’; (281) Consegnaevent il lavoro entro domanitimex . – EVENT + entro + TIMEtype −→ relType=‘‘before’’; (282) Consegnaevent il lavoro entro le 13.00timex .

References Allen, J. (1984). Towards a general theory of action and time. Artificial Intelligence, 23(2), 123–54. Bach, E. (1986). The algebra of events. Linguistics and Philosophy, 9, 5–16. Bertinetto, P. (2003). Le proprieta’ tempo-aspettuai dell’infinito in italiano. In M. G. Marcellesi and A. Rocchetti, editors, Il verbo italiano. Studi diacronici, sintattici, contrastivi, didattici, pages 113–165. Bulzoni. Caselli, T., Lenzi, V. B., Sprugnoli, R., Pianta, E., & Prodanof, I. (2011). Annotating events, temporal expressions and relations in italian: the ittimeml experience for the ita-timebank. In Linguistic Annotation Workshop, pages 143–151. Ferro, L., Mani, I., Sundheim, B., & Wilson, G. (2001). Tides temporal annotation guidelines, v. 1.0.2. MITRE Technical report MTR01W0000041, MITRE. 72

Ferro, L., L., G., Mani, I., Sundheim, B., & Wilson, G. (2002). Instruction Manual for the Annotation of Temporal Expressions. MITRE, Washington C3 Center, McLean, Virginia. Gross, G. & Kiefer, F. (1995). La structure ´ev´enementielle des substantifs. Folia Linguistica, 29(1-2), 45–65. ISO, S. W. G. (2008). ISO DIS 24617-1: 2008 Language resource management - Semantic annotation framework - Part 1: Time and events. ISO Central Secretariat, Geneva. Lavelli, A., Magnini, B., Negri, M., Pianta, E., Speranza, M., & Sprugnoli, R. (June 2005). Italian content annotation bank (i-cab): Temporal expressions (v.1.0). Technical report, ITC-irst, Trento. Pustejovsky, J. (1995). The Generative Lexicon. MIT Press. Pustejovsky, J., Castao, J., Ingria, R., Saur`ı, R., Gaizauskas, R., Setzer, A., & Katz, G. (2003). Timeml: Robust specification of event and temporal expressions in text. In Fifth International Workshop on Computational Semantics (IWCS-5).

73

Appendix A This sections reports some examples of light verb constructions and their annotation. Notice that all tokens composing a light verb construction are connected by means of the TLINK=‘‘identity’’. • dare un consiglio dare un consiglio • fare una domanda fare una domanda • fare la manutenzione fare la manutenzione • fare sconti fare sconti • avere intenzione avere intenzione • avere ragione/torto avere ragione • avere fame avere fame • fare una bomba fare una bomba 74

Appendix B We illustrate in Table ?? the set of possible temporal relations between main events in adjacent sentences. The temporal values in capital letters refers to general temporal dimensions (which includes different tenses; e.g. PAST includes tense values such as Passato Prossimo, Trapassato Prossimo, Trapassato Remoto, Passato Remoto and Imperfetto), while those in lower case refers to specific Italian grammatical tense values.

75

Tense pairs Presente - PAST Presente - Presente Presente - Presente Presente - Presente PAST - Presente FUTURE - PAST PAST - FUTURE Passato Prossimo Passato Prossimo

-

Passato Prossimo Trapassato Prossimo Passato Prossimo Trapassato Remoto Passato Prossimo Imperfetto Passato Prossimo Passato Remoto

Aspect pairs IMPERFECTIVEPERFECTIVE IMPERFECTIVEPROGRESSIVE PERFECTIVEIMPERFECTIVE IMPERFECTIVEIMPERFECTIVE PERFECTIVEIMPERFECTIVE PERFECTIVEPERFECTIVE PERFECTIVEPERFECTIVE PERFECTIVEPERFECTIVE

PERFECTIVEPERFECTIVE PERFECTIVEPERFECTIVE PERFECTIVEIMPERFECTIVE PERFECTIVEPERFECTIVE

76

Temporal relations after, includes includes before, is included includes, simultaneous before, is included after before before, after, includes, is included, begins, begun by, ends, ended by, simultaneous, i before, i after after after is included before, after, includes, is included, begins, begun by, ends, ended by, simultaneous, i before, i after

Tense pairs Trapassato Prossimo Trapassato Prossimo

Aspect pairs PERFECTIVEPERFECTIVE

Trapassato Prossimo Passato Prossimo Trapassato Prossimo Trapassato Remoto Trapassato Prossimo Imperfetto Trapassato Prossimo Passato Remoto Trapassato Remoto Trapassato Remoto

PERFECTIVEPERFECTIVE PERFECTIVEPERFECTIVE PERFECTIVEIMPERFECTIVE PERFECTIVEPERFECTIVE PERFECTIVEPERFECTIVE

-

Trapassato Remoto Passato Prossimo Trapassato Remoto Trapassato Prossimo Trapassato Remoto Imperfetto Trapassato Remoto Passato Remoto Imperfetto - Imperfetto Imperfetto - Passato Prossimo Imperfetto - Trapassato Prossimo Imperfetto - Trapassato Remoto Imperfetto - Passato Remoto

PERFECTIVEPERFECTIVE PERFECTIVEPERFECTIVE PERFECTIVEIMPERFECTIVE PERFECTIVEPERFECTIVE IMPERFECTIVEIMPERFECTIVE IMPERFECTIVEPERFECTIVE IMPERFECTIVEPERFECTIVE IMPERFECTIVEPERFECTIVE IMPERFECTIVEPERFECTIVE

77

Temporal relations before, after, includes, is included, begins, begun by, ends, ended by, simultaneous, i before, i after before after before, after, is included before before, after, includes, is included, begins, begun by, ends, ended by, simultaneous, i before, i after before before before, after, is included before includes, is included includes after, includes after, includes after, includes

Tense pairs Passato Remoto - Passato Remoto

Aspect pairs PERFECTIVEPERFECTIVE

Passato Remoto - Passato Prossimo

PERFECTIVEPERFECTIVE

Passato Remoto - Trapassato Prossimo Passato Remoto - Trapassato Remoto Passato Remoto - Imperfetto FUTURE - FUTURE

PERFECTIVEPERFECTIVE PERFECTIVEPERFECTIVE PERFECTIVEIMPERFECTIVE PERFECTIVEPERFECTIVE

Temporal relations before, after, includes, is included, begins, begun by, ends, ended by, simultaneous, i before, i after before, after, includes, is included, begins, begun by, ends, ended by, simultaneous, i before, i after after after after, is included

before, after, includes, is included, begins, begun by, ends, ended by, simultaneous, i before, i after Notice that when the Imperfetto has a PERFECTIVE reading, the set of possible temporal relations is the same as for the couple Passato Prossimo Passato Prossimo.

78