Hi!
I don't think it would be more efficient to do any api request before querying blazegraph because the api is way slower than the triple search in BlazeGraph. For exposing SPARQL for newcomers it would perhaps be
That depends a lot on which search we're doing. Some queries (especially as part of bigger queries) are not very fast in BlazeGraph, both due to query planner not being not smart and Blazegraph having different index structure than our database. Also, label-to-P/Q lookups should probably be highly cacheable, since some entities and properties are much frequently used than others. So I would see what to use depending on actual query - especially that right now Blazegraph optimizer is not perfect so semantically same queries may behave significantly different. We of course are working with Blazegraph to fix the issues, but that is another thing we should have to keep in mind when deciding which queries work best.