FUNCTIONS AND MEANINGS OF NAKEREBANARANAI, BEKI, AND HAZU AS EPISTEMIC AND DEONTIC MODALITIES

Authors

  • Diwana Fikri Aghniya

Keywords:

Epistemic Modality, Deontic Modality, Nakerebanaranai, Beki

Abstract

One of the element of language in linguistics that also observed in research is about modalities. There are many kinds of modality in Japanese language, two of them are the epistemic modality (ninshiki modariti) and deontic modality (gimu modariti) such Nakerebanaranai, Beki and Hazu. There are so many scholars, both students and teachers who can not comprehend the function and meaning of those modalities. One of the reason is the limited time that teachers have when explaining the matter to the student and the teaching materials used usually do not explain these modalities in detail. This research describes about the use of nakerebanaranai, beki and hazu as epistemic modality and deontic modality. This research is aimed to help teachers, students and other learners to understand the function and meaning of those three forms of modality in details. It is also hoped that this research may help in other studies regarding analysis about Japanese modality. A descriptive model was used in this research, which is a model that is used to describe a phenomenon that happens at present using a scientific procedure to find actual solutions or answers on the matter. The result of this study show that, as deontic modality, nakerebanaranai and beki are the form of modality that used to state about necessity. as epistemic modality, nakerebanaranai and beki are the form of modality that used to state about inevitability or certainty. As epistemic modality, hazu is the form of modality that used to state about probability and inevitability or certainty.

Downloads

Published

2021-08-16

How to Cite

Diwana Fikri Aghniya. (2021). FUNCTIONS AND MEANINGS OF NAKEREBANARANAI, BEKI, AND HAZU AS EPISTEMIC AND DEONTIC MODALITIES. Proceeding of International Conference on Japanese Studies, Language and Education, 1(1), 205-218. Retrieved from https://proceedings.aspbji.id/index.php/icjsle/article/view/21
                                                                  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_607e89427493a7_25097553(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