Speaking as a preposterous layman in this field . . like, "layman" as in "crammed some old linear algebra and calc courses a few months ago just so I could grok the basic design of these things" . .
Semantic might maybe could be the way to divide a solution up among a set of competing models. Right now, the real pain in the butt of using models for solutions (for me, anyway, aside from the unpredictability and explainability and sheer size and corpus) is that a wrong solution requires another trip back to the model (or, I guess, mastering the art of "prompt engineering", but I haven't gotten consistent guidance on how that works). Chopping up the parts of the solution, then using smaller models to compete for the chunks, then assembling the chunks and smaller models compete for that - this could be where we end up, and semantics might be one possible way to chunk things. Procedural data, after all, isn't just natural languagee: you got your part numbers, your geometries, your interwiring stuff, and lots more, all of them separately optimize-able.
The trap I always try and avoid: believing semantics are in some way an inherent or emergent property. Lots of times people in content systems have a near-religious belief in a sort of Platonic Semantics, which exists in this ether-space. Better to think of semantics as framework for NLP. My opinion, anyway. Keeps you out of a lot of trouble.
But what do I know? We could get yet another Mystery Emergent Behavior at ten trillion parameters in GPT-N that eliminates all or practically all problems with the solution, or somehow pre-guesses your future trips, or sees through your question(s) to the underlying problem. Right now, where I am, using any of this LLM stuff is strictly verboten, due to data restrictions and infosec. It's all after-hours projects at this point. So that's maybe another reason I'm thinking about smaller models - easier to get them past the gatekeepers.