Calendric_unit

http://premon.fbk.eu/resource/fn17-calendric_unit an entity of type: Concept

Words in this frame name the different parts of the calendric cycle, both man-made and natural. The Unit (e.g. Tuesday) specifies some time period as part of a specific larger temporal Whole (Tuesday of next week), or may be resolved to an exact time span by a Relative_time (next Tuesday). Jo's mother will visit on this coming Tuesday. Very frequently, the Whole or Relative_time are left out (i.e., DNI), and often should be interpreted as a time period overlapping with the communication, but more generally must be understood from context. So, for example, in the first sentence below, we can imagine that the Whole refers to a year (e.g., 1983) that was already mentioned or established in context. In the second example below, the most likely interpretation is the nearest April, whether in this year or the next, and this interpretation is best indicated by indicating the Relative_time is DNI. On April 2 , she finally found her mother . DNI. I 'll come back in April .DNI Most members of this frame can be used with iterative events, either with a plural Unit (on Tuesdays), or marked with every (every April). On Tuesday and Thursday afternoons , we have tea . In this use, when the Whole is omitted, the Whole should be marked INI. On Tuesdays , we have tea . INI Words of this frame often occur in a non-lexical construction that uses some Calendric_unit expressions to establish when an event occurred. To capture this information, we use the extra-thematic FEs Landmark_period and Trajector_event (see Temporal_collocation) on the second layer, as in the following: Last Tuesday she said I 'd have to come back . Last Tuesday she said I 'd have to come back . We do not use these FEs for cases where the temporal relationship is introduced by an overt word of the Temporal_collocation frame (like on, in, at, before, etc.). Most lexical units of this frame occur in this construction, with or without requiring a Relative_time, while some idiosyncratically do not, so information on the use with the extra-thematic FE Trajector_event is lexically specific. There are a number of non-lexical constructions that evoke this frame, including date constructions (the third, May 5), decade constructions (the oughts), year constructions (1975, 24 BCE, 10 AH, year 19, etc.), and time-of-day constructions. Although not annotated in this frame, examples such as the following show that the FEs Unit and Whole are quite appropriate: The 4th of April dawned clear and cold . December 11 was when Alix finally left . The 23rd will be snowy . DNI Nothing much happened in the 90s , did it ? DNI As described above for the lexical targets that evoke this frame, some non-lexical versions of the frame may also occur in a non-lexical Temporal_collocation construction: No-one has forgotten what happened the 5th of November ! No-one has forgotten what happened the 5th of November ! Words in this frame figure into a variety of temporal schemas, realized as constructions, primarily cases in which the Calendric_unit serves as a Landmark_period in the Temporal_collocation frame. There are families of constructions in which these words occur, including ones in which weekday names combine with day part names using particular prepositions (e.g. on Wednesday morning, cf. on Wednesday, but in the morning) and ones in which calendric terms fill the slots in multi-word expressions such as N-after-N (e.g. day after day), N-by-N (e.g. week by week), N-to-N (e.g. month to month), etc. More can be found on these in Fillmore (2002). Note, also, the connection between this frame and Frequency, specifically that many iterative adjectives and adverbs are based on calendric terms (e.g. daily, weekly, monthly, etc.).
xsd:dateTime 2001-09-13T14:54:02+02:00 
Calendric_unit 
xsd:int 229 

data from the linked data cloud