Documentation

Linglib.Theories.Semantics.Aspect.SubeventStructure

Temporal Decomposition of Events #

@cite{kiparsky-2002}

Bridges the gap between EventStructure.Template (predicate-role decomposition, no temporal information) and ViewpointAspect (temporal operators on opaque predicates, no subevent structure).

Accomplishments and achievements have internal temporal structure: an activity phase and a result phase with ordering constraints. States and activities are temporally simple. This module makes that structure explicit via TemporalDecomposition, enabling the perfect polysemy analysis in PerfectPolysemy.lean.

Key Definitions #

ViewpointAspect Bridge (§ 6–7) #

phasePred converts temporal phases into EventPred Unit Time, making them consumable by IMPF/PRFV/PERF. Key results:

Subevent Phases #

structure Semantics.Aspect.SubeventStructure.SubeventPhases (Time : Type u_1) [LinearOrder Time] :
Type u_1

The two temporal phases of a complex event (accomplishment/achievement): an activity trace (the process) and a result trace (the outcome state). The activity phase must precede or meet the result phase.

Instances For

    Temporal Decomposition #

    inductive Semantics.Aspect.SubeventStructure.TemporalDecomposition (Time : Type u_1) [LinearOrder Time] :
    Type u_1

    Temporal decomposition of an event: either simple (single runtime) or complex (runtime with internal activity + result phases).

    • States and activities are .simple: one homogeneous interval.
    • Accomplishments and achievements are .complex: the overall runtime decomposes into an activity phase and a result phase.
    Instances For

      Extract the overall runtime from any decomposition.

      Equations
      Instances For

        Extract the activity phase (only available for complex events).

        Equations
        Instances For

          Extract the result phase (only available for complex events).

          Equations
          Instances For

            Is this a complex (phased) decomposition?

            Equations
            Instances For
              @[implicit_reducible]
              Equations
              • One or more equations did not get rendered due to their size.

              VendlerClass ↔ Complexity Bridge #

              @[implicit_reducible]
              Equations
              • One or more equations did not get rendered due to their size.

              Event with Decomposition #

              structure Semantics.Aspect.SubeventStructure.DecomposedEv (Time : Type u_1) [LinearOrder Time] :
              Type u_1

              An event enriched with temporal decomposition information. Extends Event (which has runtime + sort) with subevent phase structure.

              Instances For

                Attach a simple decomposition to an event (for states/activities).

                Equations
                • One or more equations did not get rendered due to their size.
                Instances For
                  def Semantics.Aspect.SubeventStructure.Event.withComplexDecomposition {Time : Type u_1} [LinearOrder Time] (e : Events.Event Time) (phases : SubeventPhases Time) (h_act : phases.activityTrace.subinterval e.runtime) (h_res : phases.resultTrace.subinterval e.runtime) :

                  Attach a complex decomposition to an event (for accomplishments/achievements).

                  Equations
                  • One or more equations did not get rendered due to their size.
                  Instances For

                    Structural Theorems #

                    Activity precedes result in any SubeventPhases (direct accessor).

                    theorem Semantics.Aspect.SubeventStructure.complex_phases_in_runtime {Time : Type u_1} [LinearOrder Time] (rt : Core.Time.Interval Time) (phases : SubeventPhases Time) (h_act : phases.activityTrace.subinterval rt) (h_res : phases.resultTrace.subinterval rt) :

                    Both subevent phases are contained in the overall runtime of a complex decomposition (by construction).

                    A simple decomposition has no result phase.

                    A simple decomposition has no activity phase.

                    Phase Event Predicates #

                    def Semantics.Aspect.SubeventStructure.phasePred {Time : Type u_1} [LinearOrder Time] (phase : Core.Time.Interval Time) :

                    Event predicate localized to an interval: holds of eventualities whose runtime equals the given interval. Converts temporal phases of a DecomposedEv into predicates consumable by ViewpointAspect operators (IMPF, PRFV, PERF).

                    The world parameter is fixed to Unit since temporal decomposition is world-independent (following the same convention as Giannakidou.lean).

                    Equations
                    Instances For
                      theorem Semantics.Aspect.SubeventStructure.impf_phasePred {Time : Type u_1} [LinearOrder Time] (phase t : Core.Time.Interval Time) :
                      Core.IMPF (phasePred phase) () t t.properSubinterval phase

                      IMPF applied to a phase predicate reduces to the reference time being properly inside that phase interval.

                      theorem Semantics.Aspect.SubeventStructure.prfv_phasePred {Time : Type u_1} [LinearOrder Time] (phase t : Core.Time.Interval Time) :
                      Core.PRFV (phasePred phase) () t phase.subinterval t

                      PRFV applied to a phase predicate reduces to the phase interval being contained in the reference time.

                      ViewpointAspect ↔ Decomposition Bridge #

                      The imperfective paradox via temporal decomposition: IMPF on the activity phase can hold at reference times entirely before the result phase. "Was building a house" doesn't entail a house was built.

                      Counterexample: activity = [0, 10], result = [15, 20], ref = [3, 7]. The reference [3, 7] is properly inside the activity [0, 10], but entirely before the result [15, 20].

                      See also Semantics.Causation.Progressive.progressive_not_entails_perfective for the causal explanation: the initiator is type-level sufficient (progressive holds) but an intervening event can prevent token-level completion (perfective fails).

                      theorem Semantics.Aspect.SubeventStructure.perfective_full_entails_result {Time : Type u_1} [LinearOrder Time] (rt : Core.Time.Interval Time) (phases : SubeventPhases Time) (h_res : phases.resultTrace.subinterval rt) (t : Core.Time.Interval Time) (h_prfv : Core.PRFV (phasePred rt) () t) :

                      PRFV on the full event entails the result trace is within the reference time. "Built a house" entails the building was completed: the result phase is contained in any reference time that contains the whole event.

                      Proof: result ⊆ runtime (by h_res) and runtime ⊆ ref (by PRFV), so result ⊆ ref by transitivity.

                      theorem Semantics.Aspect.SubeventStructure.perfective_full_entails_activity {Time : Type u_1} [LinearOrder Time] (rt : Core.Time.Interval Time) (phases : SubeventPhases Time) (h_act : phases.activityTrace.subinterval rt) (t : Core.Time.Interval Time) (h_prfv : Core.PRFV (phasePred rt) () t) :

                      PRFV on the full event entails the activity trace is within the reference time. The process phase is also covered.

                      theorem Semantics.Aspect.SubeventStructure.perfective_full_covers_phases {Time : Type u_1} [LinearOrder Time] (rt : Core.Time.Interval Time) (phases : SubeventPhases Time) (h_act : phases.activityTrace.subinterval rt) (h_res : phases.resultTrace.subinterval rt) (t : Core.Time.Interval Time) (h_prfv : Core.PRFV (phasePred rt) () t) :

                      For complex events, PRFV on the full event entails both subevent phases are within the reference time. This is the compositional account of why perfective aspect entails completion for accomplishments.

                      theorem Semantics.Aspect.SubeventStructure.impf_activity_prfv_full_incompatible {Time : Type u_1} [LinearOrder Time] (rt : Core.Time.Interval Time) (phases : SubeventPhases Time) (h_act : phases.activityTrace.subinterval rt) (t : Core.Time.Interval Time) :
                      Core.IMPF (phasePred phases.activityTrace) () t¬Core.PRFV (phasePred rt) () t

                      IMPF on the activity phase is incompatible with PRFV on the full event at the same reference time: the progressive and perfective can't simultaneously hold for the same temporal window.

                      Proof: IMPF requires ref ⊂ activity (proper subset). PRFV requires runtime ⊆ ref. Since activity ⊆ runtime (by h_act), we get activity ⊆ ref. Combined with ref ⊆ activity (from IMPF), this forces ref = activity, contradicting the strict inequality in properSubinterval.

                      @cite{moens-steedman-1988} Event Types #

                      @cite{moens-steedman-1988} aspectual profile. Extends Vendler's three-feature AspectualProfile with ±consequent state, so the Vendler classification is inherited rather than stipulated. @cite{moens-steedman-1988}

                      Instances For
                        Equations
                        • One or more equations did not get rendered due to their size.
                        Instances For
                          Equations
                          • One or more equations did not get rendered due to their size.
                          Instances For

                            @cite{moens-steedman-1988} five-way event classification. Refines Vendler by splitting achievement along ±consequent state:

                            ClassAtomic?+ConsState?Vendler
                            statenostate
                            processnonoactivity
                            culminatedProcessnoyesaccomplishment
                            culminationyesyesachievement
                            pointyesno(none)

                            @cite{moens-steedman-1988}

                            Instances For
                              @[implicit_reducible]
                              Equations
                              Equations
                              • One or more equations did not get rendered due to their size.
                              Instances For

                                Canonical profile for each M&S event type. The VendlerClass is inherited from AspectualProfile via extends — accessible as c.toProfile.toVendlerClass without a separate mapping function.

                                Equations
                                Instances For
                                  @[implicit_reducible]
                                  Equations
                                  • One or more equations did not get rendered due to their size.

                                  Points and culminations share a Vendler class (achievement) but differ in ±consequent state — exactly the conflation Moens & Steedman identify.

                                  Points are telic (achievements) but lack consequent states — the reason Vendler's classification is too coarse for the perfect.

                                  Unified When-Clause Semantics (@cite{moens-steedman-1988}) #

                                  What when accesses in each event type. M&S's key claim: when has a single meaning (locate the main clause at the culmination), with apparent ambiguity arising from different nucleus structures. @cite{moens-steedman-1988}

                                  Instances For
                                    @[implicit_reducible]
                                    Equations
                                    Equations
                                    • One or more equations did not get rendered due to their size.
                                    Instances For

                                      The Nucleus (Tripartite Event Structure) #

                                      structure Semantics.Aspect.SubeventStructure.Nucleus (Time : Type u_1) [LinearOrder Time] :
                                      Type u_1

                                      The @cite{moens-steedman-1988} nucleus: tripartite event structure for events with a culmination point. Makes the culmination explicit — it is implicit in SubeventPhases as the boundary between activityTrace and resultTrace.

                                      SubeventPhases: |---activity---| |---result---|
                                      Nucleus: |---prep-------|•c |---cons-----|
                                                                       ↑
                                                               explicit culmination
                                      

                                      @cite{moens-steedman-1988}

                                      Instances For

                                        The M&S event type determined by which components are present.

                                        Equations
                                        • One or more equations did not get rendered due to their size.
                                        Instances For
                                          def Semantics.Aspect.SubeventStructure.Nucleus.toSubeventPhases {Time : Type u_1} [LinearOrder Time] (n : Nucleus Time) (prep cons : Core.Time.Interval Time) (h_prep : n.prepProcess = some prep) (h_cons : n.consState = some cons) :

                                          A full nucleus (both prep and cons present) yields SubeventPhases. The ordering proof follows from transitivity through the culmination.

                                          Equations
                                          • n.toSubeventPhases prep cons h_prep h_cons = { activityTrace := prep, resultTrace := cons, activity_precedes_result := }
                                          Instances For
                                            theorem Semantics.Aspect.SubeventStructure.Nucleus.full_is_culminatedProcess {Time : Type u_1} [LinearOrder Time] (n : Nucleus Time) {p c : Core.Time.Interval Time} (hp : n.prepProcess = some p) (hc : n.consState = some c) :

                                            A full nucleus has event type culminatedProcess.

                                            theorem Semantics.Aspect.SubeventStructure.Nucleus.hasConsState_of_consState {Time : Type u_1} [LinearOrder Time] (n : Nucleus Time) {c : Core.Time.Interval Time} (hc : n.consState = some c) :

                                            A nucleus with consequent state has M&S's consequent state feature.