Page Comparison

...

Question answering is the most common use - case in conversational applications. Orbita Answers is a system that uses a fact-based AI approach to answering questions from information modeled in a knowledge graph.

...

Give a name to your Knowledge Base (Note that creating two knowledge bases with the same name will create conflicts while deploying the project to Alexa/Dialogflow.). You can create your own content schema and assign it to your knowledge base to have custom fields in the Facts screen. You can select a content schema from the dropdown list if already created, else select default for the multimodal content editor.

...

1. In the Settings screen, select the Relationship tab and click icon.

2. Enter the Relationship name and click ADD.

   

3. In On the Relationship creation page, you can add synonyms to the Relationship name.

   

...

All the topics and relationships will be stored as slots in Orbita. Identifying the slots from a given utterance is the key for Answers to work effectively. Though the regular NLPs identify the slots from the utterance, sometimes they fail to extract all the slots values/entities you require.

We recommend using the Orbita NLP node with the Answers Manager node, in Experience Designer, to yield better results from Answers.

...

Best practices and tips for authoring a knowledge base of facts to power a conversational question-answer experience using Orbita Answers.

Best practices for creating

...

A topic is a word or phrase (most likely be a noun, noun phrase, proper noun, or compound noun).
Example: Sunburn

...

a Knowledge base

• For each Knowledge base, three slots and one intent will be autogenerated

  • Slots

    1. <Knowledge base name>_TOPICS

    2. <Knowledge base name>_RELATIONSHIP

    3. <Knowledge base name>_INTERROGATIVE
       The below screenshot captures the autogenerated slots for the Knowledge base named FAQ.

       Image Added

  • Intents

    1. OA<Knowledge base name>INTENT
       The below screenshot captures the autogenerated intent for the Knowledge base named FAQ.

       Image Added

• Ensure the knowledge base name is unique and doesn't match with the names from other modules such as Taxonomy.

Best practices for creating Topics

• A topic is a word or phrase (most likely be a noun, noun phrase, proper noun, or compound noun).
  Example: Sunburn

• A topic name doesn’t necessarily need to be a word in a dictionary. It could be a business name, brand name, product name, etc.

• A topic name should be the singular form of the noun (e.g. Chemical Burn vs Chemical Burns). Orbita handles lexemes (burns, burning, burned, etc.)

• There are cases where a topic might be a verb (e.g. Eat) and should be the dictionary form of the word (e.g. Eat, rather than eats, eating, ate. This form is also called the lemma form).

• A topic can be an acronym (e.g. COPD). When specifying an acronym, use single letters with no spaces.

• A topic may contain multiple concepts (e.g. Cancer and Hunger) but generally should focus on a single concept (e.g. Cancer, Hunger). A best practice is to think about the questions people will ask about your knowledge base – if someone is likely to ask about each concept separately, make it two topics. If they’ll ask about two concepts in the question (e.g. Will I lose my appetite during cancer treatments?), it’s okay to have a topic with two concepts.

...

• A synonym is a word or phrase that means exactly or nearly the same as the topic (most likely be a noun, noun phrase, proper noun, or compound noun).

• A synonym should be the singular form of the noun (e.g. Chemical Burn vs Chemical Burns). Orbita handles lexemes (burns, burning, burned, etc.)

• A synonym should reflect the way people express topics conversationally and will not necessarily be a synonym that exists in a dictionary for your topic (e.g. severe allergic reaction or covered in hives may be synonyms for the topic anaphylaxis). Research ways people refer to concepts conversationally by looking at web search logs, call center logs, talking with customer support, etc.

• A synonym should consider the question someone might ask about the topic. E.g. Assume a knowledge base of First Aid content, where a topic/relationship is Anaphylaxis/Causes. Consider the question What causes severe hives? ”severe hives” would be a synonym for Anaphylaxis

• A synonym name doesn’t necessarily need to be a word in a dictionary. It could be a business name, brand name, product name, etc.

• A synonym name can be an acronym. When specifying an acronym, use single letters with no spaces (e.g. COPD)

• A good synonym reflects ways people refer to the concept conversationally.

Best practices for Facts

• A fact should contain a topic and can have one or more relationships but the fact should not be a duplicate in terms of topic and relationships mapped to it.

How to model new content for Orbita Answers?

...