Fixes SF 101 Manchester OWL Syntax Parser doesn't do precedence
correctly

a and b or c was parsed as a and (b or c)
This was caused by the parsing done as
parseIntersection -> parseUnion -> parseNonNaryClassExpression
which basically assigns precedence to 'or'
Reversing the calls fixes the issue.