Inverse properties can signal sloppy modeling. With triples, linking in “both directions” is unnecessary because you can match on triple patterns directly — you don’t need to navigate “from” a known entity “to” an unknown entity. Yes, reasoning with inverse properties can strain query performance, but I think the zeroth order issue is that it may signal sloppy modeling, a “let’s toss in anything anyone could possible want” approach rather than a model with clear conceptual integrity and thus in good service as data documentation. So, there may be a good reason for given inverse properties, but I’d consider it a “model smell” that signals a need for closer examination (and again, the result of examination may be that the inverses are justified)
