Graph projections

Neo4j Graph Platform
1

Hi,

Kindly clarify the following:

  1. Does projecting all the nodes and relationships of a graph also project their properties?

  2. Is it not possible to use type properties as one of the features while training a graph algorithm?

  3. I have a KG from an ecommerce website. I have user node, session node, orders node and their relationships etc. I am trying to use link prediction algorithm to predict the link between an order node and a recipient node. Is there any useful resource that I could refer?

I am a beginner in neo4j GDS. Any help is appreciated. Thanks in advance!

2

Thanks @Cobra for the reply,
3. I went through the example actually and was able to understand quite a bit. The issue I am not able to relate it to my use case which is link pred. Main problem is how to split the graph for training and testing. i.e., I have a particular relationship and this relationship is missing between few nodes. I need my train set to have a graph with the relation and test set to be without the relation. So that the model is able to predict missing relations of the test graph. There are only a few uses which are very simple.

3

Hello @MeghanaS :blush:

  1. No, you must specify the properties you want to project: example.
  2. No, but you can use One-Hot Encoding function to use string values in Machine Learning algorithms.
  3. You can start with the Product recommendation engine using FastRP and kNN example.

In addition, I advise you to do these free courses before starting:

  1. Introduction to Neo4j Graph Data Science
  2. Neo4j Graph Data Science Fundamentals

Regards,
Cobra

4

I think you have two options:

  1. If you want to use Link Prediction algorithms of GDS, you don't need to split your graph into train/test/validation.
  2. If you want to use Machine Learning, you should have a look here where everything is explained.

Regards,
Cobra

5

1. This makes sense. But here it is used only for a pair of similar nodes. My use case is to predict relation between nodes but of different type. Let me define my problem statement first.
I have a graph something like this.
(:session)-[:contains]->(:order), (:customer)-[:has]->(:session),(:order)-[:has]->(:product), (:order)-[:to]->(:relation)
There are many customers who have placed orders. Some of the orders specify to whom the order was intended to (relation) i.e., mother/father etc. and some orders do not. For these orders my intention is to predict to whom the order was likely intended to. Any suggestions?

6

I guess you can start without a machine learning pipeline, last time I worked with a recommendation engine I used Adamic Adar to recommend sessions of formation. Here are some articles if you need more explanation:

You can compute the score between orders which will give you a score then create the relation between the order and the relation with the score in it. The issue with this method is that you will have the same score for everyone. For heterogeneous graph, I think you will have to use machine learning pipeline.

Regards,
Cobra

7

I did an estimate before training, and the mem available is less than required.

8

Yes correct. But again 2 issues here .

  1. I want to the train set to have only positive samples i.e., graph containing the relation between order & relation. Test set to have only negative samples. i.e., graph not containing the relation between order & relation.
    The way we do in classic ML and DL. It should be able to learn from the train and predict them in test. But here I see both train and test will have negative samples.
  2. I do not want the model to predict missing links between every other node rather it should be able to predict between only order node and relation node
    How do I achieve this?
9

You need to increase the the power allocated to the database and you should estimate the procedure before starting it.

10

You should have a look at this setting.

11

I have deleted the unused nodes/relations in the projected graph. Lets see😊

12

Yes. I have a heterogenous graph and need to use a pipeline.

13

Then, if you follow this example, it should help you solve your use case.

14

Okay.. Is it not possible to make the model predict only for specified nodes before hand?

Also,

Below is an example of exhaustive search prediction given in the doc. Here relationshipType means that the graph is filtered on KNOWS relation. There would be no disconnected nodes for prediction in such case am I right? Please correct me if I am wrong.
CALL gds.beta.pipeline.linkPrediction.predict.mutate('myGraph',
{ modelName: 'lp-pipeline-model',
relationshipTypes: ['KNOWS'],
mutateRelationshipType: 'KNOWS_EXHAUSTIVE_PREDICTED',
topN: 5, threshold: 0.45 })YIELD relationshipsWritten, samplingStats

15

So, I was able to train the model and the model is now ready for predictions.
There are 2 ways of prediction: Exhaustive search, Approximate search. The first one predicts for all unconnected nodes and the second one applies KNN to predict. I do not want both; rather I want the model to predict the link only between 2 specific nodes 'order' node and 'relation' node.. Is there any way to achieve this?

16

I know link prediction algorithms can predict between two nodes but I don't know for machine learning pipeline.

Yeah, according to the documentation: relationshipTypes means: Filter the named graph using the given relationship types.

Regards,
Cobra

17

With the stream method, you can add a WHERE clause after the YIELD to only return the score between the nodes you are interested in.

18

Hi again,
How do I query the relationships from a projected graph? i.e., I have a few relationships predicted from my LP model and I want to see between how many nodes is this new relation created.

19

You can use this but it is in alpha tiers.

20

Hi,
I resumed the work today and am able to stream my predicted relationships and their probabilities also. Below is the code

CALL gds.graph.streamRelationshipProperty(

'mygraph',

'predictied_probablity_score',

['predicted_relationship_name']

)

YIELD

sourceNodeId, targetNodeId, relationshipType, propertyValue

RETURN

gds.util.asNode(sourceNodeId).name as source, gds.util.asNode(targetNodeId).name as target, relationshipType, propertyValue

ORDER BY source ASC, target ASC

The issue here is now, I am getting all the source and target nodes as NULL.