Where I find Trilium to shine though, is when, after linking notes to one other for a little while, you realise "Well, I have a bunch of them that relate to `People`, others to `Products`, and, oh, a bunch of `Customers` as well, wouldn't it be nice if those were sharing the same properties?" (like People:{"Lives in", "Date of birth", "Partner of"…}, Customer:{"Address", "Contracts":-Multiple-, …}).

When you reach that point you can use Inheritance (from the hierarchy) and/or Composition (from Template notes) so that all your "People"-like or "Customer"-like notes share the same properties, and you can then easily manage them as data, giving the same organisational and queryable power of a RDBMS without having to commit on a data model from the get go (it evolves with you as you refine the inherited or templated attributes).

I think any sufficiently large collection of notes eventually reaches a point where it self-organises around a set of "Reference notes" more often linked to, and this is where Trilium saves you a ton of time instead of giving you more house-keeping work (good luck maintaining those "Reference notes" in sync with each-other in a system like Logseq or Obsidian, been there, done that).