A careful analysis of the Knowledge Graph helps in detecting errors in your questions and the path associated with the same that hamper the user experience.
Knowledge Graph Diagnosis tool helps you to identify any inefficiencies in your knowledge graphs and suggest possible corrective actions. Note that these are just guidelines and you need to further analyze the recommendations before going ahead with any changes.
The Knowledge Graph provides an option to initiate an inspection of the graph:
- This option is available only for the in-development version of the Knowledge Graph where there are one or more FAQs added to the graph.
- The analysis considers the thresholds and other configurations of the Knowledge Graph.
- The analysis issues a warning if any node contains more than 25 questions and an advisory to the effect that the training fails if there are more than 100 questions in any node.
- You can invoke the diagnosis, by clicking Inspect on the Knowledge Graph screen.
- The platform analyzes the knowledge graph and provides a report of the analysis.
- You have an option to Re-run the analysis or Export the report. The export option downloads the report in JSON format.
- The inspect report shows an overview of the number of issues found under various categories (see below for details)
- The various categories are grouped as:
- Error – Errors are incorrect graph definitions that need an immediate fix.
- Warnings – When rectified, it help improves intent detection. A maximum of 50 warnings is displayed.
- Suggestions – When implemented, it helps in the better organization of your KG. A maximum of 10 suggestions is displayed.
- Click each category to view the detailed report.
- Chances are that there are more than 50 warnings or 10 suggestions, but only the first 50/10 occurrences of the issue are listed. You must fix the same and re-run the analysis to view the next set.
Following are the fields that are displayed in the report:
|Questions added to incorrect paths||Error||
||Modify the path to include the terms in the question.|
|Long-chain of terms with the questions present only at the last term in the chain||Suggestion||
||Reduce the path by avoiding unimportant terms or merge relevant terms.|
|Identical terms with a common ancestor||Suggestion||
||Move the child terms above their parent terms to avoid duplication|
|Paths without any questions||Suggestion||
||Remove the path if you do not intend to add any questions to this path|
|Redundant alternate questions||Suggestion||
||Rephrase alternate questions to include wider coverage|
|A large number of questions added to the root term||Suggestion||
||Move the questions to the appropriate paths|
|Unusually long paths||Warning||
||Reduce the path by avoiding unnecessary terms or merging relevant terms.|
|Questions at the root node that can be moved to better paths||Warning||
||Move the question to the suggested path|
|Questions with common words that are not used as terms||Warning||
||Extend the current path using the suggested extension|
|Questions that match multiple paths||Warning||
||Review the paths to avoid possible ambiguity scenarios|
|Identical sibling nodes||Warning||
||Merge the identical terms|