The Function Of Antecedents In Japanese Relative Clauses

Authors

  • Ngurah Indra Pradhana Udayana University
  • I Nyoman Udayana Udayana University
  • Ketut Artawa Udayana University
  • Ketut Widya Purnawati Udayana University

Keywords:

antecedents, relative clause, japanese

Abstract

This research focuses on a type of clause known as a relative clause. In Japanese, relative clauses are called?????( meishi shuushoku setsu ). In this study, the function of antecedents in Japanese relative clauses is presented. the function of antecedents in Japanese relative clauses using a theoretical approach from Dixon (2010). The result of this research is Japanese relative clauses cannot be separated from their antecedent function. The antecedent in Japanese relative clauses is always located after the verb or verb phrase. The types of verbs that can precede an antecedent in Japanese relative clauses in this study include state verbs (????/Jyoutai doushi ) and activity verbs (????/Dousha doushi ). In this study, four types of antecedent functions were found in Japanese relative clauses, including topic, subject, object and oblique functions. One way to differentiate the function of the four antecedent functions is to look at the particle that follows the antecedent in the relative clause. Antecedents in Japanese relative clauses can be nouns and pronouns.

Downloads

Published

2024-11-14

How to Cite

Ngurah Indra Pradhana, I Nyoman Udayana, Ketut Artawa, & Ketut Widya Purnawati. (2024). The Function Of Antecedents In Japanese Relative Clauses. Proceeding of International Conference on Japanese Studies, Language and Education, 5(1), 12-17. Retrieved from https://proceedings.aspbji.id/index.php/icjsle/article/view/81

Issue

Vol. 5 No. 1 (2024): Proceeding of International Conference on Japanese Studies, Language and Education (ICJSLE)

Section

Articles 
                                                                  ADOConnection.CacheExecute(3600, SELECT 				o.submission_id, 				MAX(s.context_id) AS journal_id, 				MAX(i.date_published) AS i_pub, 				MAX(p.date_published) A..., Array[2]) % line  132, file: DAO.inc.php
                                                               DAO.retrieveCached(SELECT 				o.submission_id, 				MAX(s.context_id) AS journal_id, 				MAX(i.date_published) AS i_pub, 				MAX(p.date_published) A..., Array[2], 3600) % line   91, file: ArticleSearchDAO.inc.php
                                                            ArticleSearchDAO.getPhraseResults(Object:Journal, Array[1], null, null, , 500, 1) % line  207, file: SubmissionSearch.inc.php
                                                         SubmissionSearch._getMergedPhraseResults(Object:Journal, Array[1], , null, null, 500, 1) % line  146, file: SubmissionSearch.inc.php
                                                      SubmissionSearch._getMergedKeywordResults(Object:Journal, Array[4], , null, null, 500, 1) % line  194, file: SubmissionSearch.inc.php
                                                   SubmissionSearch._getMergedPhraseResults(Object:Journal, Array[4], null, null, null, 500, 1) % line  146, file: SubmissionSearch.inc.php
                                                SubmissionSearch._getMergedKeywordResults(Object:Journal, Array[3], null, null, null, 500, 1) % line  132, file: SubmissionSearch.inc.php
                                             SubmissionSearch._getMergedArray(Object:Journal, Array[1], null, null) % line  263, file: SubmissionSearch.inc.php
                                          SubmissionSearch.retrieveResults(Object:Request, Object:Journal, Array[1], null, null, null, Object:DBResultRange, Array[1]) % line   92, file: RecommendBySimilarityPlugin.inc.php
                                       RecommendBySimilarityPlugin.callbackTemplateArticlePageFooter(Templates::Article::Footer::PageFooter, Array[3]) % line  107, file: HookRegistry.inc.php
                                    HookRegistry.call(Templates::Article::Footer::PageFooter, Array[3]) % line 1254, file: PKPTemplateManager.inc.php
                                 PKPTemplateManager.smartyCallHook(Array[1], Object:Smarty_Internal_Template) % line   43, file: 42362804174f266c598cdb32c3208fc745b92101^1c372c95cd85572e0fbc9a53d0323a0b229cfc78_0.app.frontendpagesarticle.tpl.php
                              content_6a3770fdf00ec2_07411404(Object:Smarty_Internal_Template) % line  123, file: smarty_template_resource_base.php
                           Smarty_Template_Resource_Base.getRenderedTemplateCode(Object:Smarty_Internal_Template) % line  114, file: smarty_template_compiled.php
                        Smarty_Template_Compiled.render(Object:Smarty_Internal_Template) % line  216, file: smarty_internal_template.php
                     Smarty_Internal_Template.render(false, 1) % line  232, file: smarty_internal_templatebase.php
                  Smarty_Internal_TemplateBase._execute(Object:Smarty_Internal_Template, null, 42362804174f266c598cdb32c3208fc745b92101, null, 1) % line  134, file: smarty_internal_templatebase.php
               Smarty_Internal_TemplateBase.display(frontend/pages/article.tpl, null, 42362804174f266c598cdb32c3208fc745b92101, null) % line  922, file: PKPTemplateManager.inc.php
            PKPTemplateManager.display(frontend/pages/article.tpl) % line  281, file: ArticleHandler.inc.php
         ArticleHandler.view(Array[1], Object:Request) % line  391, file: PKPRouter.inc.php
      PKPRouter._authorizeInitializeAndCallRequest(Array[2], Object:Request, Array[1], false) % line  231, file: PKPPageRouter.inc.php
   PKPPageRouter.route(Object:Request) % line  143, file: Dispatcher.inc.php
Dispatcher.dispatch(Object:Request) % line  279, file: PKPApplication.inc.php
PKPApplication.execute() % line   68, file: index.php