paul.thomas is spot on here, it depends upon the queries you plan to run. Having :Action nodes (that can be multi-labeled if you like) as stand-ins for these kinds of groupings makes sense.
Keep in mind that this type of graph isn't really well modeled as a property graph. For example, you have multiples of the same nodes, such as Donald Trump. Usually with property graphs your data is normalized, so you would have a single node to represent an entity and not duplicates, yet for the purposes of display you would seem to need multiples of the same nodes, otherwise you would have the same Donald Trump node with relationships to each of these, in ways that doesn't covey information clearly the way your example graph does.
All these things lead me to believe you're not really looking for a database, but a visualization tool for a graphical presentation, where that presentation is different enough from the property graph model that you're likely to run into frustration trying to use it for something it's not designed for.
Is that the case? If not, we'd need to know more about the kinds of queries you're planning to run. You may also want to look at different visualization tools that may be able to convey richer views of your data.
