At my last company, the system that eventually became our Knowledge Graph started out as RDF. It seemed like a great fit, but we didn't really have much luck. T

At my last company, the system that eventually became our Knowledge Graph started out as RDF. It seemed like a great fit, but we didn't really have much luck. There was an unnecessarily complicated process for schema definition and the SPARQL engine we chose (on top of PostgreSQL) wasn't ready for a production load (e.g. was not performant). I really liked the concept and we borrowed the "triple" approach in our next iterations, but we really didn't get any benefit from using RDF. Quite possible it was our fault.