FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W3192806760> ?p ?o ?g. }

• W3192806760 abstract "Introduction . Amongst the syntactical issues which have been investigated for more than 100 years we would like to explore the question of using nominative and ablative case in the structure of complex nominative predicate with explicated component бути . This question was studied by I. Vihovanets, M. VIntonIv, K. Gorodenska, A. Zagnitko, N. Ivanitska, M. Kapas, K. Kosenko, O. Kurilo, L. Litvin, O. Sinyavskiy, S. Smerichinskiy, M. Sulima, O. Sulima etc. Purpose . The purpose of this research is to study the dynamics of using such constructions as « бути + N. case / A. case» (with explicated verbal linking) in Ukrainian language in XIX - XXI centuries. Results . The first attempt to solve the problem of the usage of ablative predicative case in Ukrainian is connected with O. Potebnya. He declared that the reason of raising the ablative predicate case can be explained by the necessity of distinguishing the parts of the sentences. He believed that nominative predicative case is immanent for Ukrainian language. Scientific discussions about the possibilities/impossibilities in Ukrainian language continued till 1920s. In 1920s there were two opinions about predicative constructions бути + N. case / A. case. On the one hand the choice between бути + N. case and бути + A. case with explicated verbal linking бути depends on speaker’s communicative intention: it was recommended to use the nominative predicative case for expressing the constant feature and ablative predicative case for inconstant features. According to another approach it was recommended to avoid the ablative predicative case. The opinion about synonimical usage of predicative constructions бути + N. case and бути + A. case existed in Ukrainian linguistics till the beginning of XXI century. Originality . During the end of XIX - ХХ centuries linguists semantically distinguished the usage of the analyzed constructions: nominative for constant features and ablative for inconstant features. So, constructions бути + N. case and бути + A. case functioned as synonimical. At the beginning of XXI century I. Vihovanets and K. Gorodenska noticed variety in analyzed predicative constructions: there are no restrictions in the usage of both predicative forms of the noun. Conclusion . So, the opinions about the usage of such constructions as бути + N. case and бути + A. case have changed greatly. Today it is possible to use both nominative and ablative predicative cases with explicated verbal linking бути ." @default.
• W3192806760 created "2021-08-16" @default.
• W3192806760 creator A5054166772 @default.
• W3192806760 date "2017-03-09" @default.
• W3192806760 modified "2023-09-22" @default.
• W3192806760 title "PREDICATIVE CONSTRUCTIONS «БУТИ + N. case / A. case» IN UKRAINIAN LITERATURY LANGUAGE: THEORETICAL ASPECT" @default.
• W3192806760 hasPublicationYear "2017" @default.
• W3192806760 type Work @default.
• W3192806760 sameAs 3192806760 @default.
• W3192806760 citedByCount "0" @default.
• W3192806760 crossrefType "journal-article" @default.
• W3192806760 hasAuthorship W3192806760A5054166772 @default.
• W3192806760 hasConcept C129131279 @default.
• W3192806760 hasConcept C138885662 @default.
• W3192806760 hasConcept C140146324 @default.
• W3192806760 hasConcept C199360897 @default.
• W3192806760 hasConcept C21931767 @default.
• W3192806760 hasConcept C2776397901 @default.
• W3192806760 hasConcept C2778854177 @default.
• W3192806760 hasConcept C41008148 @default.
• W3192806760 hasConcept C41895202 @default.
• W3192806760 hasConcept C5468625 @default.
• W3192806760 hasConceptScore W3192806760C129131279 @default.
• W3192806760 hasConceptScore W3192806760C138885662 @default.
• W3192806760 hasConceptScore W3192806760C140146324 @default.
• W3192806760 hasConceptScore W3192806760C199360897 @default.
• W3192806760 hasConceptScore W3192806760C21931767 @default.
• W3192806760 hasConceptScore W3192806760C2776397901 @default.
• W3192806760 hasConceptScore W3192806760C2778854177 @default.
• W3192806760 hasConceptScore W3192806760C41008148 @default.
• W3192806760 hasConceptScore W3192806760C41895202 @default.
• W3192806760 hasConceptScore W3192806760C5468625 @default.
• W3192806760 hasIssue "2" @default.
• W3192806760 hasLocation W31928067601 @default.
• W3192806760 hasOpenAccess W3192806760 @default.
• W3192806760 hasPrimaryLocation W31928067601 @default.
• W3192806760 hasRelatedWork W1492245536 @default.
• W3192806760 hasRelatedWork W1778414994 @default.
• W3192806760 hasRelatedWork W2001778056 @default.
• W3192806760 hasRelatedWork W2043747717 @default.
• W3192806760 hasRelatedWork W2288599060 @default.
• W3192806760 hasRelatedWork W2295193854 @default.
• W3192806760 hasRelatedWork W234739210 @default.
• W3192806760 hasRelatedWork W2736971493 @default.
• W3192806760 hasRelatedWork W2773269990 @default.
• W3192806760 hasRelatedWork W2792470508 @default.
• W3192806760 hasRelatedWork W2801578130 @default.
• W3192806760 hasRelatedWork W2981920365 @default.
• W3192806760 hasRelatedWork W3008350757 @default.
• W3192806760 hasRelatedWork W3029132449 @default.
• W3192806760 hasRelatedWork W3085377463 @default.
• W3192806760 hasRelatedWork W3106384729 @default.
• W3192806760 hasRelatedWork W588533756 @default.
• W3192806760 hasRelatedWork W619837615 @default.
• W3192806760 hasRelatedWork W624127754 @default.
• W3192806760 hasRelatedWork W631538424 @default.
• W3192806760 isParatext "false" @default.
• W3192806760 isRetracted "false" @default.
• W3192806760 magId "3192806760" @default.
• W3192806760 workType "article" @default.