Questions phrased so the answer cannot be a feature name.
Vendors in this market answer honestly in my experience. The problem is almost never that somebody misled a buyer; it is that the buyer asked questions a product page could answer. "Do you support SKOS" gets a yes from everyone. "Export this model and show me the file" gets a different conversation.
What follows is organised by who should ask it, because the questions that catch real problems come from people who are often absent from the evaluation.
Ask these first, because they are the hardest to fix later and the least likely to be volunteered.
Open standards vs proprietary graph platforms covers why these four decide more than anything else on the list.
These separate products that look identical in a demo.
The first question is the single most revealing one on this page, and it is rarely asked. Reconstructing a past definition requires the version, the approval and the content to be joined, and many products store all three and join none of them.
Ask these with whoever runs the system that will actually call the platform, because nobody else will raise them.
Three, and the second is the one that produces surprises in year two.
"What is in the enterprise tier?" Governance features sitting above the tier you are buying is a common and legitimate packaging choice. It is also a cost you should see now.
"How does pricing move as consumers grow?" A platform priced per seat behaves very differently from one priced per call once AI systems start resolving terms at volume.
"What does support actually cover?" Specifically whether modelling help is included or billed, because the first year is mostly modelling.
The pattern is consistent enough to be useful. Good answers are specific and often include a limitation.
| You ask | A good answer | A warning sign |
|---|---|---|
| Export with constraints | Produces a file, names what is omitted | "Fully supported" with no file |
| What did this say before | Shows the prior version with its approver | Opens an audit log of events |
| Resolve from curl | Runs it, shows the latency | Describes an integration pattern |
| Approval latency | Quotes a real customer's number | Describes the workflow designer |
A vendor who volunteers a limitation usually earns more trust than one who does not. Every product in this category has limitations, and the hidden ones are the ones you meet later.
Who needs to be in the room?Four people, and two of them are usually missing.
An evaluation without the last two optimises for the purchase instead of the operation, and the product that wins is the one that demos best. How to evaluate a knowledge graph platform covers the surrounding process.
Earlier than feels polite, and the exit questions belong in the first conversation.
The usual sequence puts portability last, somewhere near contract negotiation, by which point the team has invested weeks in a preferred product and nobody wants the answer to be awkward. Asking on the first call costs nothing and changes which products reach the trial.
Teams that run it in that order finish faster, because the expensive discoveries happen while the shortlist is still cheap to change.
So what should I take away?Ask for demonstrations instead of confirmations. Export a model and read the file. Change a definition and ask what it said before. Resolve a term from curl and time it. Every one of those produces an answer a feature list cannot.
TopQuadrant is one of the vendors you would be asking, so apply all of this to us. Our knowledge graph platform is built on RDF, OWL and SHACL specifically so the export question has a good answer, and the right response to that sentence is to test it. If we fail one of these, finding out during a trial serves you better than finding out in year three.