GLiNER2
Hacker ApprovedInformation extraction model in AI tools
Open-source non-LLM model for entity extraction, recommended as fast, cheap and CPU-friendly; critics say its Python code ignores software engineering practices.
Open-source non-LLM model for entity extraction, recommended as fast, cheap and CPU-friendly; critics say its Python code ignores software engineering practices.
15 people gave an opinion
- recommend it
- 12
- criticize it
- 3
- approval share
- 80%
Recommended in 5 of 13 months
- November 2025: not recommended
- December 2025: recommended
- January 2026: not recommended
- February 2026: not recommended
- March 2026: recommended
- April 2026: not recommended
- May 2026: recommended
- June 2026: not recommended
- July 2026: not recommended
- August 2026: not recommended
- September 2026: recommended
- October 2026: recommended
- November 2026: not recommended (month in progress)
Why it carries the badge
- 12 people recommend itNeeds 10 or more, met.
- 4 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 5 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Fast, cheap, CPU-first
“its faster, cheaper and better”
Comment from 5 May 2026 in “AI inference infrastructure built on small and nano models” “Love the focus on CPU-first.”
Comment from 5 Mar 2026 in “GLiNER2: Unified Schema-Based Information Extraction” Strong non-LLM entity extraction
“Fantastic (non LLM) models for entity extraction.”
Comment from 6 Dec 2025 in “Why are your models so big? (2023)” “GLiNER is a really great research work.”
Comment from 6 Mar 2026 in “GLiNER2: Unified Schema-Based Information Extraction”
What people warn about
Each mark is one comment
Python code quality problems
“Sounds like a great model which is hobbled by a bunch of mundane python programming issues”
Comment from 8 Mar 2026 in “GLiNER2: Unified Schema-Based Information Extraction” “Feels like it's written by ML people not following python software engineering practices.”
Comment from 6 Mar 2026 in “GLiNER2: Unified Schema-Based Information Extraction”
What people said
12 of the 16 comments that mention it, newest first. Each links to the original comment.
“At around 4 classes already LLM-based classifiers (Jev/Laya/GLiNER et al) start falling behind”
“gliner2 (and especially 2.5) can do _most_ of things that jev can, minus the flashy demos”
“It is also open source and I think also has some good usage.”
“They opened a lot of people's eyes, including my own”
“outperforming OpenAI's Privacy Filter and all existing GLiNER PII variants”
“its faster, cheaper and better”
“Sounds like a great model which is hobbled by a bunch of mundane python programming issues”
“there is a dependency on gliner1”
“GLiNER is a really great research work.”
“Feels like it's written by ML people not following python software engineering practices.”
“Love the focus on CPU-first.”
“Fantastic (non LLM) models for entity extraction.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.