Gabriel Delattre
04/13/2026, 7:35 PM"bts informatique à Paris" "je cherche une licence pro en alternance à Bordeaux" "école d'ingénieurs près de Lyon pour faire de l'IA"And I want to extract structured entities out of these before hitting Typesense:
{
"diploma": "BTS",
"field": "informatique",
"city": "Paris",
"query": "informatique"
}
So that city and diploma become filter_by parameters, and the remaining intent becomes the actual q — instead of throwing the whole raw string at Typesense and hoping for the best.
What I've considered so far:
Dictionary lookup for cities (BAN communes dataset, ~35k entries)
Regex patterns for diploma types (BTS, BUT, licence, master, `prépa`…)
Is there a lightweight, JS-compatible approach that handles all three entity types / facet (city + diploma + field) well enough for production, without needing a full ML runtime?
I know about the natural language search which has landed in v29 but it seems a bit overkill for a quick Named Entity Recognition.Gabriel Delattre
04/13/2026, 7:36 PMAlan Martini
04/13/2026, 9:21 PMq, filter_by, and sort_by parameters. If you absolutely want to avoid LLM dependency, the dictionary + regex approach you described is the standard lightweight alternative, but Typesense offers no built-in NER outside of NLS.Apoorv Singh
04/20/2026, 3:27 PMAlan Martini
04/22/2026, 2:05 PM