Take your time and beware of objectivity of article. Vendors try to lure you in. Following has some good info (but a Neo4j bias): https://dzone.com/articles/rdf-triple-stores-vs-labeled-prop...
Also, both those articles are a bit old: RDF* ([2],[3]) is a new extension for RDF that makes it easier to accomplish the same kind of things you can do with property graphs. RDF4j has support for RDF* in the roadmap! [4].
To me, the fact that RDF is 1) a simpler and more general model and 2) an open standard with multiple free and commercial implementations; makes RDF a more a attractive option than locking into a single proprietary implementation like Neo4j.
--
1: http://www.snee.com/bobdc.blog/2018/04/reification-is-a-red-...
2: http://olafhartig.de/slides/RDFStarInvitedTalkWSP2018.pdf
3: http://blog.liu.se/olafhartig/2019/01/10/position-statement-...
One of the most interesting picks: RDF4j (java based). It can connect to a lot of different SPARQL servers, but the rdf4j Native Store should be good enough for data sets in the order of the "100 million triples", according to the docs.
I don't know much about it, but not long ago they announced integrated support for "federated queries", which means that if you data set can't fit in a single node, they have a solution to query different servers in the same query [2].
I'm slowly learning through the forest of related technologies, one of the most useful is SHACL [3], which is a language to validate and extract pieces of the graph that match a pattern (very loosely, think a "schema" for graphs).
1: https://en.wikipedia.org/wiki/List_of_SPARQL_implementations
2: https://rdf4j.org/news/2019/10/15/fedx-joins-rdf4j/
3: https://rdf4j.org/documentation/programming/shacl/