The distributed Grakn knowledge base presents two different ways to obtain insight on a large dataset:
- It intelligently aggregates large amounts of information. Graql allows you to specify what you want, and analytics allows you to do it at scale. For example, finding out the mean number and standard deviation of vehicles owned by companies (not individuals), no matter how big the dataset.
- The structure of the knowledge base contains valuable information about the importance of entities and also the communities they form. This is achieved by computing the number of relationships that certain entities take part in, and using this as a measure of how popular they are. An example of this can be seen on the Moogi website, which uses only the structure of the graph to rank the results.
What Can I do With Analytics?
The functionality breaks down into two main tasks:
- computing statistics related to numeric resources
- interrogating the structure of the knowledge base.
Currently you can compute the
std (standard deviation) and
sum of resources attached to entities. This
can also be achieved on a subgraph, which is a subset of the types in your dataset. For example, you can specify queries to find the mean age of people in a knowledge base:
compute mean of age in person;
We cover this topic more in our documentation page on statistics.
At the moment we have a simple algorithm for determining
- centrality measure (degree)
- paths between nodes (shortest path)
- clusters or communities (connected components).
The Knowledge Graph According to Analytics
Graql analytics functionality is accessed via the
compute query in the Graql language. In order to fully understand the
syntax, an in-depth understanding of the knowledge base is needed, so we will dive into some details here.
Analytics only “sees” the instances of types, but is aware of the schema. Therefore, if your knowledge base has a type
then the instances of this:
Hermione Newman and
Barbara Herchelroth can be counted using analytics.
Often you are not interested in the whole knowledge base when performing calculations, and it is possible to specify a subgraph (a subset of your data to work on) to Graql.
For example, a knowledge base may contain groups, people and the relationships between them, but these can be excluded by specifying a subgraph using the
To count just people:
compute count in person;
Consider the simple knowledge base below that includes types and instances (some are entities and some are relationships).
Analytics will consider every instance in the knowledge base, and therefore, will not consider the type nodes
marriage, (coloured in pink).
To compute the count on this knowledge base without specifying any subgraph, we call the following, which would return the number 4:
Analytics has counted all of the instances of the types, which are specific people and the nodes representing the marriage relationship.
A subgraph is defined in analytics by using the types. For example, we could specify a subgraph that includes only
person like this:
compute count in person;
and this would return the number 3. The analytics will now operate on can be seen below.
We may also specify a subgraph for efficiency (so we do not have to count the things we are not interested in). The algorithm for computing the degree is one example. If we execute the following query, the number of arrows (edges) attached to each node is returned:
compute degrees in person, marriage;
In the example below this would be 1 for Jacob Young, 2 for Barbara Herchelroth, 1 for John Newman and 0 for the rest because we do not count the arrows indicating type, only arrows labelled with
This knowledge base also happens to include the parentship relationship, but we have ignored this and only found out the number of marriages a person has taken part in for any size of graph.