{"id":56736,"date":"2023-04-19T09:17:36","date_gmt":"2023-04-19T08:17:36","guid":{"rendered":"https:\/\/developer.kore.ai\/v10-1\/?p=56736"},"modified":"2023-04-19T09:17:36","modified_gmt":"2023-04-19T08:17:36","slug":"knowledge-graph-terminology","status":"publish","type":"post","link":"https:\/\/developer.kore.ai\/v10-1\/docs\/bots\/bot-builder-tool\/knowledge-task\/knowledge-graph-terminology\/","title":{"rendered":"Knowledge Graph Terminology"},"content":{"rendered":"<p><span style=\"font-weight: 400\">This article explains the terminology for <\/span><a href=\"https:\/\/developer.kore.ai\/v10-1\/docs\/bots\/bot-builder-tool\/knowledge-task\/creating-a-knowledge-graph\/\"><span style=\"font-weight: 400\">building a Knowledge Graph<\/span><\/a><span style=\"font-weight: 400\"> within the XO Platform. This terminology applies to both the Few-Shot and the Ontology KG Models unless otherwise specified. <\/span><a href=\"https:\/\/developer.kore.ai\/v10-1\/docs\/bots\/bot-builder-tool\/knowledge-task\/knowledge-ontology\/\"><span style=\"font-weight: 400\">Learn more about Knowledge Graph Types<\/span><\/a><span style=\"font-weight: 400\">.<\/span><\/p>\n<div class=\"w-separator size_small with_line width_default thick_1 style_solid color_border align_center\"><div class=\"w-separator-h\"><\/div><\/div>\n<h1><span class=\"ez-toc-section\" id=\"Terms_or_Nodes\"><span style=\"font-weight: 400\">Terms or Nodes<\/span><\/span><\/h1>\n<p><span style=\"font-weight: 400\">Terms or Nodes are the building blocks of an ontology and are used to define the fundamental concepts and categories of a Knowledge Graph.<\/span><\/p>\n<p><span style=\"font-weight: 400\">You can organize the terms in a hierarchical order to represent the flow of information in your graph. You can create, organize, edit, and delete terms and set term types to facilitate intent identification\u00a0<\/span><\/p>\n<p><b>The Knowledge graph is limited to 20 thousand nodes\/terms and 50 thousand FAQs.<\/b><\/p>\n<h2><span class=\"ez-toc-section\" id=\"NodeTerm_Hierarchy\"><span style=\"font-weight: 400\">Node\/Term Hierarchy<\/span><\/span><\/h2>\n<p><span style=\"font-weight: 400\">For easier representation, we identify node\/term hierarchy using the following names:<\/span><\/p>\n<h3><span class=\"ez-toc-section\" id=\"Root_TermNode\">Root Term\/Node<\/span><\/h3>\n<p><span style=\"font-weight: 400\">The <\/span><b><i>Root Term\/Node<\/i><\/b><span style=\"font-weight: 400\"> forms the topmost term of your Ontology. A Knowledge Graph contains only one root node, and all other nodes in the ontology become its child nodes. The <\/span><i><span style=\"font-weight: 400\">Root <\/span><\/i><span style=\"font-weight: 400\">node takes the name of the VA by default, but you can change it as needed. In an Ontology-based KG, this node is not used for path qualification or processing. Path qualification starts from first-level nodes.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400\">For Ontology-Based graphs, it is best to organize your FAQs into a clear structure, so we don\u2019t recommend adding them at the <\/span><i><span style=\"font-weight: 400\">Root <\/span><\/i><span style=\"font-weight: 400\">node. You can, however, add a maximum of 100 FAQs if required.\u00a0<\/span><\/p>\n<h3><span class=\"ez-toc-section\" id=\"First-level_TermNode\">First-level Term\/Node<\/span><\/h3>\n<p><span style=\"font-weight: 400\">The immediate next-level nodes after the <\/span><i><span style=\"font-weight: 400\">Root <\/span><\/i><span style=\"font-weight: 400\">node are known as <\/span><b><i>First-Level Term\/Node<\/i><\/b><span style=\"font-weight: 400\">. There can be any number of first-level nodes in a graph. We recommend using first-level nodes to represent high-level terms, such as the names of departments, functionalities, etc. <\/span><span style=\"font-weight: 400\">For example, in a Travel Assistant, you might have a first-level node called <\/span><i><span style=\"font-weight: 400\">Reservation<\/span><\/i><span style=\"font-weight: 400\">, which can be structured by functionality into subnodes such as: <\/span><i><span style=\"font-weight: 400\">Cancel <\/span><\/i><span style=\"font-weight: 400\">and <\/span><i><span style=\"font-weight: 400\">Update<\/span><\/i><span style=\"font-weight: 400\">.<\/span><\/p>\n<h3><span class=\"ez-toc-section\" id=\"Leaf_TermNode\">Leaf Term\/Node<\/span><\/h3>\n<p><span style=\"font-weight: 400\">Any node at any level starting with the 2nd is called a <\/span><b><i>Leaf Term\/Node<\/i><\/b><span style=\"font-weight: 400\">.<\/span><\/p>\n<table style=\"background-color: #fffbea\">\n<tbody>\n<tr>\n<td><strong><em>Note<\/em><\/strong><em><span style=\"font-weight: 400\">: This hierarchical organization of nodes is for your convenience to keep related questions together. The Knowledge Graph Engine does not consider any parent-child relation while evaluating the questions for a match. The hierarchy does not influence the FAQ matching process since all the nodes are considered the same way, irrespective of their position.<\/span><\/em><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><a ref=\"magnificPopup\" href=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v10-1\/wp-content\/uploads\/sites\/35\/20230419085301\/image4.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-56727 size-full\" title=\"Hierarchy\" src=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v10-1\/wp-content\/uploads\/sites\/35\/20230419085301\/image4.png\" alt=\"\" width=\"742\" height=\"579\" srcset=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v10-1\/wp-content\/uploads\/sites\/35\/20230419085301\/image4.png 742w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v10-1\/wp-content\/uploads\/sites\/35\/20230419085301\/image4-300x234.png 300w\" sizes=\"auto, (max-width: 742px) 100vw, 742px\" \/><\/a><\/p>\n<h2><span class=\"ez-toc-section\" id=\"TermNode_Types\"><span style=\"font-weight: 400\">Term\/Node Types<\/span><\/span><\/h2>\n<p><span style=\"font-weight: 400\">Functionally, there are three types of Terms\/Nodes.<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400\"><b>Default<\/b><span style=\"font-weight: 400\">: Default terms do not have any particular considerations in shortlisting qualified paths in Ontology-based KGs.\u00a0<\/span><\/li>\n<li style=\"font-weight: 400\"><b>Mandatory<\/b><span style=\"font-weight: 400\">: When you mark a term as <\/span><i><span style=\"font-weight: 400\">Mandatory<\/span><\/i><span style=\"font-weight: 400\">, paths associated with it are shortlisted for ranking only if the user\u2019s utterance includes the mandatory term or its synonyms.<\/span><\/li>\n<li style=\"font-weight: 400\"><b>Organizer<\/b><span style=\"font-weight: 400\">: This term type can be marked as part of the Knowledge Graph to organize the ontology and help qualify FAQs even when they don\u2019t contain the specific terms.<\/span><span style=\"font-weight: 400\"><br \/>\n<\/span><a ref=\"magnificPopup\" href=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v10-1\/wp-content\/uploads\/sites\/35\/20230419085247\/image1.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-56718 size-full\" title=\"Term Types\" src=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v10-1\/wp-content\/uploads\/sites\/35\/20230419085247\/image1.png\" alt=\"\" width=\"1024\" height=\"707\" srcset=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v10-1\/wp-content\/uploads\/sites\/35\/20230419085247\/image1.png 1024w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v10-1\/wp-content\/uploads\/sites\/35\/20230419085247\/image1-300x207.png 300w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/a><\/li>\n<\/ul>\n<div class=\"w-separator size_small with_line width_default thick_1 style_solid color_border align_center\"><div class=\"w-separator-h\"><\/div><\/div>\n<h1><span class=\"ez-toc-section\" id=\"Tags\"><span style=\"font-weight: 400\">Tags<\/span><\/span><\/h1>\n<p><span style=\"font-weight: 400\">For each term\/node, you can add custom <\/span><a href=\"https:\/\/developer.kore.ai\/v10-1\/docs\/bots\/nlp\/knowledge-graph\/#Tags\"><span style=\"font-weight: 400\">tags<\/span><\/a><span style=\"font-weight: 400\">. Tags work exactly like terms but are not displayed in the Knowledge Graph ontology to avoid clutter. You can add synonyms and traits to tags as you do to terms.<\/span><\/p>\n<div class=\"w-separator size_small with_line width_default thick_1 style_solid color_border align_center\"><div class=\"w-separator-h\"><\/div><\/div>\n<h1><span class=\"ez-toc-section\" id=\"Synonyms\"><span style=\"font-weight: 400\">Synonyms<\/span><\/span><\/h1>\n<p><span style=\"font-weight: 400\">The Knowledge Graph allows you to add <\/span><a href=\"https:\/\/developer.kore.ai\/v10-1\/docs\/bots\/nlp\/knowledge-graph\/#Synonyms\"><span style=\"font-weight: 400\">Synonyms <\/span><\/a><span style=\"font-weight: 400\">for terms to include all possible alternative forms. Adding synonyms reduces the need for training the VA with alternative questions.<\/span><\/p>\n<p><span style=\"font-weight: 400\">For example, the reservation node in our previously-mentioned Travel Assistant may have the following synonyms added to it: booking, order, purchase, etc.\u00a0<\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"Synonym_Types\"><span style=\"font-weight: 400\">Synonym Types<\/span><\/span><\/h2>\n<p><span style=\"font-weight: 400\">When you add a synonym for a term or a tag in the Knowledge Graph, you can add it as a local or global synonym. Local synonyms (or <\/span><b><i>Path Level Synonyms<\/i><\/b><span style=\"font-weight: 400\">) apply to the term only in that particular path, whereas global synonyms (or <\/span><b><i>Knowledge Graph Synonyms<\/i><\/b><span style=\"font-weight: 400\">) apply to the term even if it appears on any other path in the ontology.<\/span><\/p>\n<p><span style=\"font-weight: 400\">After v. 7.2 of the XO Platform, you can also use <\/span><b><i>Bot Synonyms<\/i><\/b><span style=\"font-weight: 400\"> inside the Knowledge Graph engine for path qualification and question matching. With this setting, you need not recreate the same synonyms in Bot Synonyms and KG Synonyms.<\/span><\/p>\n<div class=\"w-separator size_small with_line width_default thick_1 style_solid color_border align_center\"><div class=\"w-separator-h\"><\/div><\/div>\n<h1><span class=\"ez-toc-section\" id=\"Traits\"><span style=\"font-weight: 400\">Traits<\/span><\/span><\/h1>\n<p><span style=\"font-weight: 400\">A trait is a collection of typical end-user utterances that define the nature of a question. <\/span><a href=\"https:\/\/developer.kore.ai\/v10-1\/docs\/bots\/nlp\/traits\/\"><span style=\"font-weight: 400\">Learn more<\/span><\/a><span style=\"font-weight: 400\">.<\/span><\/p>\n<p><span style=\"font-weight: 400\">A trait is applied to multiple terms across your Bot Ontology.<\/span><\/p>\n<table style=\"background-color: #fffbea\">\n<tbody>\n<tr>\n<td><em><strong>Note<\/strong><span style=\"font-weight: 400\">: Traits also help you filter nodes based on associated user utterances. So, if the user types an utterance that is present in a trait, the assistant only searches the nodes to which the trait is applied. If the utterance is present in any other node to which the trait is not applied, the node is ignored.<\/span><\/em><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<div class=\"w-separator size_small with_line width_default thick_1 style_solid color_border align_center\"><div class=\"w-separator-h\"><\/div><\/div>\n<h1><span class=\"ez-toc-section\" id=\"Intents\"><span style=\"font-weight: 400\">Intents<\/span><\/span><\/h1>\n<p><span style=\"font-weight: 400\">A VA can respond to a given question with an FAQ or the execution of a Dialog Task.<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400\"><b>FAQ<\/b><span style=\"font-weight: 400\">: The question-answer pairs must be added to relevant nodes in your ontology. A maximum of 50k FAQs is permissible. A question is asked differently by different users, and to support this, you must associate multiple alternate forms for each question. Preceding an alternate question with || will allow you to enter patterns for FAQs (after the v.7.2 release).<br \/>\n<a ref=\"magnificPopup\" href=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v10-1\/wp-content\/uploads\/sites\/35\/20230419085307\/image5.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-56730 size-full\" title=\"FAQ\" src=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v10-1\/wp-content\/uploads\/sites\/35\/20230419085307\/image5.png\" alt=\"\" width=\"1024\" height=\"372\" srcset=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v10-1\/wp-content\/uploads\/sites\/35\/20230419085307\/image5.png 1024w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v10-1\/wp-content\/uploads\/sites\/35\/20230419085307\/image5-300x109.png 300w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/a><br \/>\n<\/span><\/li>\n<li style=\"font-weight: 400\"><b>Task<\/b><span style=\"font-weight: 400\">: Linking a Dialog task to a KG Intent helps leverage the capabilities of the Knowledge Graph and Dialog tasks to handle FAQs that involve complex conversations.<br \/>\n<a ref=\"magnificPopup\" href=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v10-1\/wp-content\/uploads\/sites\/35\/20230419085251\/image2.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-56721 size-full\" title=\"Task\" src=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v10-1\/wp-content\/uploads\/sites\/35\/20230419085251\/image2.png\" alt=\"\" width=\"1024\" height=\"258\" srcset=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v10-1\/wp-content\/uploads\/sites\/35\/20230419085251\/image2.png 1024w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/v10-1\/wp-content\/uploads\/sites\/35\/20230419085251\/image2-300x76.png 300w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/a><\/span><\/li>\n<\/ul>\n<div class=\"w-separator size_small with_line width_default thick_1 style_solid color_border align_center\"><div class=\"w-separator-h\"><\/div><\/div>\n<table style=\"width: 100%;border-collapse: collapse;background-color: #dffbea\">\n<tbody>\n<tr>\n<td style=\"width: 100%\">\n<h1><span class=\"ez-toc-section\" id=\"Notes_on_the_Few-Shot_Knowledge_Graph\"><em><span style=\"font-weight: 400\">Notes on the Few-Shot Knowledge Graph<\/span><\/em><\/span><\/h1>\n<ol>\n<li style=\"font-weight: 400\"><em><span style=\"font-weight: 400\">For Few-Shot graphs, you can add all your FAQs to the Root node because the LLM does not require an ontology.<\/span><\/em><\/li>\n<li style=\"font-weight: 400\"><em><span style=\"font-weight: 400\">Default <\/span><span style=\"font-weight: 400\">terms are not available in Few-Shot Knowledge Graphs. The only exception is when you switch from an Ontology Graph, in which case existing <\/span><span style=\"font-weight: 400\">Default <\/span><span style=\"font-weight: 400\">terms are stored as such until updated. Afterward, <\/span><span style=\"font-weight: 400\">Default <\/span><span style=\"font-weight: 400\">terms become <\/span><span style=\"font-weight: 400\">Organizer <\/span><span style=\"font-weight: 400\">terms and can be set as <\/span><span style=\"font-weight: 400\">Mandatory<\/span><span style=\"font-weight: 400\">.<\/span><\/em><\/li>\n<li style=\"font-weight: 400\"><em><span style=\"font-weight: 400\">Path Level Synonyms are only supported for <\/span><span style=\"font-weight: 400\">Mandatory <\/span><span style=\"font-weight: 400\">Terms and for Tags.<\/span><\/em><\/li>\n<\/ol>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<div class=\"w-separator size_small with_line width_default thick_1 style_solid color_border align_center\"><div class=\"w-separator-h\"><\/div><\/div>\n","protected":false},"excerpt":{"rendered":"<p>This article explains the terminology for building a Knowledge Graph within the XO Platform. This terminology applies to both the Few-Shot and the Ontology KG Models unless otherwise specified. Learn more about Knowledge Graph Types. Terms or Nodes Terms or Nodes are the building blocks of an ontology and are used to define the fundamental&#8230;<\/p>\n","protected":false},"author":27,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[33],"tags":[],"class_list":["post-56736","post","type-post","status-publish","format-standard","hentry","category-knowledge-task"],"_links":{"self":[{"href":"https:\/\/developer.kore.ai\/v10-1\/wp-json\/wp\/v2\/posts\/56736","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/developer.kore.ai\/v10-1\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/developer.kore.ai\/v10-1\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/developer.kore.ai\/v10-1\/wp-json\/wp\/v2\/users\/27"}],"replies":[{"embeddable":true,"href":"https:\/\/developer.kore.ai\/v10-1\/wp-json\/wp\/v2\/comments?post=56736"}],"version-history":[{"count":4,"href":"https:\/\/developer.kore.ai\/v10-1\/wp-json\/wp\/v2\/posts\/56736\/revisions"}],"predecessor-version":[{"id":56776,"href":"https:\/\/developer.kore.ai\/v10-1\/wp-json\/wp\/v2\/posts\/56736\/revisions\/56776"}],"wp:attachment":[{"href":"https:\/\/developer.kore.ai\/v10-1\/wp-json\/wp\/v2\/media?parent=56736"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/developer.kore.ai\/v10-1\/wp-json\/wp\/v2\/categories?post=56736"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/developer.kore.ai\/v10-1\/wp-json\/wp\/v2\/tags?post=56736"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}