An inferred network creates direct graph relationships from an indirect pattern already present in a graph. Rather than treating the derived relationship as original data, it summarizes what the observed pattern means for a particular analysis. The relationship type, direction, and properties must reflect domain assumptions. section 2.3.3
A retweet graph provides a practical example. Users publish tweets, and other users retweet them; this path can be translated into a direct AMPLIFY relationship between the relevant users. Under the assumption that retweets are positive interactions, AMPLIFY represents promotion of another user's content and the increased reach it receives. section 2.3.3 section 6.0
Listing 6.1 Describing the translation of the indirect retweet pattern to a direct AMPLIFY relationship
MATCH (s:User)-[:PUBLISH]->()-[:RETWEETS]->()<-[:PUBLISH]-(t:User) CREATE (s)-[:AMPLIFY]->(t);
This Cypher pattern matches an indirect retweet path and creates a direct AMPLIFY relationship, producing a user-to-user projection from tweet-level activity. section 6.0
An inferred AMPLIFY network can retain useful analytical meaning:
- It is directed when the direction of promotion is meaningful. section 2.3.3
- It is weighted when the relationship stores the number of retweets between users; one retweet gives weight 1, while repeated retweets increase it. section 2.3.3 section 6.0
- It forms a monopartite network containing User nodes and AMPLIFY relationships, removing Tweet nodes from the projected view. section 6.0
- It supports influence and community analysis, such as finding users with highly sharable content or users who mutually promote content. section 2.3.3 section 6.0
Projecting retweets into amplification
Start with User–PUBLISH–Tweet and RETWEETS relationships. Match each retweet pattern, create a direct AMPLIFY relationship between the associated users, and count repeated retweets as a relationship property. PageRank on the resulting network can consider both retweet volume and who performed the retweet. section 6.0 section 2.3.3
