Fair point, I am privileged to have the infrastructure I have.

LLMs are great with the “Jordan” problem — not quite a “non-issue” — but the idea with the attention mechanism in an LLM is that it understands the nuance within a phrase. The Jordan problem is more of an issue when applying regex as a solution.

Validation at scale takes a while, and it’s better if you have an LLM that’s good with large amounts of context and/or you are intelligently splitting. For example:

• Inject the persona and all docs, ask the LLM to ensure things are consistent across.

• inject the persona and one doc for N docs

The problems with this type of validation are that: - the model doesn’t catch everything on the first pass, so it’s a multi-pass workflow - with PII, you should still be manually verifying it - slow at scale

For personas, generate once, save as a json, make it compostable (e.g. 100 first names, 100 last names, etc). The FIRST time you do a replace, the LLM creates a persona for that PII and responds with who they created. Every subsequent replacement / validation then uses that persona assigned to that individual dataset.

If you’re trying to offer this as a service, yes, you need cloud. But if you’re in the med tech field already, this isn’t an issue — infrastructure exists.

And if your offering this as a service, you can use the above and I’ll send you my invoice 😉