Sometimes the automatic parser makes mistakes, or the information provided in the claim text is simply insufficient for the computer. This is seen as graphs that are not technically 100% correct. Luckily, these problems can usually be solved quite easily.

Let's take an example: 

This will provide the following graph (with parser version 8/2019):

The graph will as such provide quite good search results, but the feature "liquid level sensor" is not positioned as under the "coffee cup" due to the wording "there is also provided..." in which a human reader interprets "there" as referring to the "coffee cup" but the machine doesn't. The wording is unnecessarily written in the relation under the "handle".

By selecting the "liquid level sensor" and pressing Tab on the keyboard and selecting the relation and using backspace to shorten the relation fixes the problem, as shown here: 

The resulting graph is technically accurate and concise and probably provides also slightly better search results:

In addition to indenting and editing items, you can outdent, delete and create new items. Shifting items up and down will not affect search results but can make the graph more logical and readable.  For more information on editing the graphs, please see this article.

New product versions will gradually improve automatic graph quality, but to some degree human supervision is advisable. Learn more about editting a graph in this detailed Video tutorial.

Did this answer your question?