I can imagine that with extensive tuning, BlazeGraph provides a good database. Just don't expect it to have the polish and convenience of a modern RDBMS or a shiny NoSQL store :)
https://lists.wikimedia.org/pipermail/wikidata-tech/2015-Mar...
Here's a spreadsheet showing WikiData's evaluation of each candidate graph database:
https://docs.google.com/spreadsheets/d/1MXikljoSUVP77w7JKf9E...
Basically as far as I can see, the main reason BlazeGraph was chosen was this: [they] had me out to their office (a house an hour and half from mine)[3]
I'm sure BlazeGraph is fine. We were doing a very similar evaluation at the same time, and the Titan situation screwed us over too. But we took a look at BlazeGraph after Wikidata chose it, and found it pretty rudimentary at that time.
[1] https://phabricator.wikimedia.org/T90101
[2] "As you can also see we didn't finish filling them all out. But we've still pretty much settled on BlazeGraph anyway. Let me first explain what BlazeGraph is and then defend our decision to stop spreadsheet work" https://lists.wikimedia.org/pipermail/wikidata-tech/2015-Mar...
[3] https://lists.wikimedia.org/pipermail/wikidata-tech/2015-Mar...
There's now an updated user's guide on the wiki: https://wiki.blazegraph.com/wiki/index.php/Main_Page
and additional code samples: https://github.com/blazegraph/blazegraph-samples/
I would happily pay for a developer license or something like that.
Blazegraph is a very niche product and requires a lot of time for setting it up and adjusting it for your workload.
If Blazegraph peaks your interest then you should also look into Yarc platform by Cray.
Should you want to look more into graphs, but don't want to spend endless nights just trying to load your data then I would recommend Stardog, which has just been a pleasure to work with.