Replies: 1 comment
-
Interesting. I don‘t think you need to represent them as different types. It should be sufficient to just temporary remove the links to the purchase history of nodes you are currently training from. I think this is similar to the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I’m working on a node classification problem to predict which users are likely to make a purchase and become a customer. The input includes a social graph with edges indicating user-to-user friendship, and node features such as demographic and purchase history of all users. The idea of using graph learning here is that for a user with no purchase history, if most of her friends have made purchases, she should be more likely to convert to a customer in the future.
My thinking is during training, we should hide purchase history features for the target node itself. Otherwise, the model will trivially learn to predict customer based off the existence of purchase history. On the other hand, we can use the full feature set including purchase history from their friends per the idea mentioned above.
If all of these make sense, my question is how to hide certain features for the target node during training? Do I need to use heterogeneous graph learning and treat the target node and neighboring node as two different types? Any code sample, papers, or discussion pointers would be appreciated!
Beta Was this translation helpful? Give feedback.
All reactions