A knowledge graph is then nothing more than a graph database, with well-known relationships between entities.
We have actually already started building a knowledge graph in Chapter 2, Cypher Query Language. Indeed, the graph we built there contains the Neo4j-related repositories and users on GitHub: it is a representation of the knowledge we have regarding Neo4j ecosystem.
So far, the graph only contains two kinds of information:
- The list of repositories owned by the Neo4j organization
- The list of contributors to each of these repositories
But our knowledge can be extended much beyond this. Using the GitHub API, we can go deeper and, for instance, gather the following:
- The list of repositories owned by each contributor to Neo4j, or the list of repositories they contributed to
- The list of tags assigned to each repository
- The list of users each of these contributors follow
- The list of users following each contributor
For example, let&apos...
