I make a graph about costumer, but it is a bipartite graph, each customer doesn't related to other customer? Is that counts as Knowledge graph?
1 Answer
$\begingroup$
$\endgroup$
3
If the links in your graph represent customer relationship then your graph is not bi-partite, its uni-partite. Think of it as customer1-link-customer2 kind of relationship but you only have one set of distinct entities making it a uni-partite graph. Check the definition for bi-partite graph here. You need to have two disjoint sets to call it a bi-partite graph.
An example: If you have multiple types of link between customers (lets say follower and friend) then you have two sets of disjoint entities- Customers and Type of relationship. In that scenario you have a bi-partite graph with customers on one side and type of link on the other.
As for the knowledge graph, it is really an abstract idea. You first need to define what is the goal of having the bi-partite or any kind of graph. Does it answer a generic question that can be queried every time the need arises. If the graph solution you offer, meets certain standards (like querying, adding/deleting/updating any nodes/links) and answers a general question about the population then it becomes a knowledge graph.
Also, not every node needs to be directly linked to another node to qualify as part of a knowledge graph.
-
1$\begingroup$ thank you. To clarify, the links in my graph represent customer relationship with each of their attribute, and not to other customer. Let's say customer A is part of Class 1, and customer B is part of Class 1 to. So i have three nodes: customer A, customer B, and Class 1. But there is no link between customer A and B $\endgroup$Ocean– Ocean2025-06-02 15:24:44 +00:00Commented Jun 2, 2025 at 15:24
-
$\begingroup$ A few more considerations before you can call it a bi-partite graph: 1. Do you have two disjoint partitions of customers where same customer can never be a part of both partitions? 2. Do you need for more than one class of link between customer (eg: class1='follower', class2='friend' etc) or does a single class suffice? $\endgroup$SharmaTu– SharmaTu2025-06-04 06:52:37 +00:00Commented Jun 4, 2025 at 6:52
-
$\begingroup$ I'm making the relation based on the customer attributes, each customer having three attributes. Example: attribute 1 is "tariff type", attribute 2 is region", and "attribute 3 is class". $\endgroup$Ocean– Ocean2025-06-05 03:56:00 +00:00Commented Jun 5, 2025 at 3:56