elastic / elastic/docs-content

Rework NLP docs section: classical NLP vs search/retrieval models

Open
#7,605 1 comment 0 reactions 1 assignee Claimed by @kosabogi View on GitHub
Confidence: 0.8 Effort: 1 Impact: 2 ml nlp Reach: 3 Team:Developer
Dominant language
No language data
Stars
47
Forks
261
Avg merge
3d 12h
Merged PRs (30d)
116

Description

### Problem

The [NLP](https://www.elastic.co/docs/explore-analyze/machine-learning/nlp) section (and its children) no longer matches what it contains.

It originally covered classical NLP / text analytics (NER, text classification, zero-shot, extractive QA, fill-mask, language identification, plus HF/Eland deploy workflows). Over time it also absorbed search/retrieval models such as ELSER, E5, Elastic Rerank, and the Jina family (embeddings, multimodal, rerankers, reader)—which are not classical NLP tasks.

That naming and IA makes it harder to find true NLP content, and overlaps with Elastic Inference and Solutions → Search docs for the same retrieval models.

Related: #7603

### Possible directions (high level)

Either keep a renamed/broader models section under Machine learning, **or** split classical NLP from search/retrieval models (for example toward Elastic Inference / Search). Exact scope and IA TBD.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.