Skip reverse geocode query on /phone, rely on dbpedia sparql query instead

Getting a consistent address description via geocoding was convoluted,
and didn't make sense given the summary that dbpedia could otherwise
provide.

Also, issue a second sparql query if the first sends back a redirect.
Syntax highlighting endpoint