Publications

Detailed Information

Constraints on the Perfective [V-ko (iss-)] in Korean : With Reference to a Present State Reading

Cited 0 time in Web of Science Cited 0 time in Scopus
Authors

Chae, Hee-Rahk

Issue Date
2020-12
Publisher
Language Education Research Center, Seoul National University
Citation
Language Research, Vol.56 No.3, pp. 309-357
Keywords
[V-ko iss-] in Koreanresultative constructiontelicitypast time interpretationpresent state reading
Abstract
Korean [… V-ko iss-] is ambiguous between progressive and resultative meanings. We assume that it is ambiguous in three ways: P(rogressive)-reading, R(esultative)-reading and p(seudo)-R-reading constructions. These constructions allow different sets of predicates in the [… V] position. Most previous analyses agreed that telic predicates are responsible for the (traditional) resultative reading. However, this telicity condition does not adequately predict the occurrence of the reading: i) p-R predicates are not necessarily telic, and ii) not all telic predicates can trigger the R construction. The aim of this paper is to provide a set of constraints operating on the R construction under the understanding that p-R predicates should be excluded in advance. First, only those telic predicates that can indicate a present state in their past tense form can trigger the R construction. In addition, we show the need to posit two more constraints: a syntactic/semantic constraint and a pragmatic constraint. We further show that the present approach based on these new observations can properly characterize the R construction while excluding the P and p-R constructions. In dealing with the present state reading, we face the recalcitrant phenomenon of a theta role change in the subject of the predicate concerned.
ISSN
0254-4474
Language
English
URI
https://hdl.handle.net/10371/174167
DOI
https://doi.org/10.30961/lr.2020.56.3.309
Files in This Item:
Appears in Collections:

Altmetrics

Item View & Download Count

  • mendeley

Items in S-Space are protected by copyright, with all rights reserved, unless otherwise indicated.

Share