Look into user-triggered changes of the query

[Daniel-Mietchen]

E.g.
if there is a LIMIT, allow them to adjust it easily via a form field or slider, implemented in JavaScript on the Scholia end.
Or if there is a UNION or a property path and the query times out, they could drop one of those and rerun then.

Of course, they could do such adjustments directly in the Query Service but the idea here is to not force people onto meddling with SPARQL if they are not comfortable with it.