Hi Robert,
A few clarification before so you can make sure RDF is the right fit for your need:
RDF is a data exchange format (representing everything as a set of triples (s, p, o), which all together forms a graph.
Then there are some languages that defines some particular triples to which some meaning are associated, i.e., a vocabulary a community is agreeing on when sharing data. RDFS and OWL are some examples.
You can visualise a set of RDF triples in various ways such as text files in different serialisation format, e.g., Turtle or RDF/XML. Or you can use a great tool like OntoText which reads your RDF triples to show you a nice graph.
Usually when modelling with RDF people tend to think that what they have defined in RDF as an RDFS or OWL class is an entity and therefore should appear as a node in the visual graph. However, what you really do in this cas is inserting the triple (myThing rdf:type rdfs:Class). And if I remember well the graph visualizer from OntoText by default shows the raw rdf triples. It also often happened that some basic RDF triples are preloaded when creating a triplestore (e.g., OWL or RDFS triples). Hence, the default graph vis will show them.
With this lengthy response I hope to clarify that if your only goal is to visualise your data as a graph, RDF might be a complex choice.
That being said, OntoText graph vis lets you define the SPARQL queries to execute for each "click" action on do when manipulating the graph vis.
I am telling you all this from my little previous experience with OntoText and my understanding. I hope it helps and I am very happy to discuss.
Good luck š