Allow changing the back-end for NER filters #66
MatheusRich
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
An alternative to the current ML approach could be using a local-running (or an open source LLM hosted on a server you own) to identify information like people names and locations. LLMs are particularly helpful because they're flexible (even if faulty) and a simple prompt is enough to "train it" on a new task.
I propose that we allow changing the back-end for NER filters. Maybe instead of passing a
model_path, we could build the NER model in the configuration file:and
LLMBasedNERcould implement the required API and do it's work whatever way it wants to. This also has the benefit of only building the NER model once and paying that cost during initialization.Alternatively, this could be achieve by disabling NER filters and providing a new kind of custom filter. The filter interface should be:
#callmethod that filters an input and returns a#labelmethod to build the mappingBeta Was this translation helpful? Give feedback.
All reactions