I used a hybrid NER pipeline to find the most loved chef knives on Reddit

Back to stories Open in a window

I used a hybrid NER pipeline to find the most loved chef knives on Reddit

Hey HN,

I'm a developer and a bit of a knife nerd. I wanted to find out which chef knives are truly the best according to the expert community at r/chefknives. Instead of just counting keywords, I built a multi-pass analysis pipeline to extract brands, models, and steels, and then run sentiment analysis on them.

I analyzed over 1,000 posts from the subreddit. You can see the full results and play with the data here: https://new.knife.day

The Technical Approach: A Hybrid NER Pipeline The core of the project is a 5-phase pipeline that combines fast, deterministic matching with the contextual power of LLMs.

Phase 1: Known Entity Recognition (Fuse.js)

First, I do a quick pass using Fuse.js for fuzzy string matching.

It checks the text against a pre-loaded list of ~465 brands, ~8,700 models, and 50 steel types from an external API.

This is super fast and catches 80-90% of the common entities like "Wüsthof," "Shun," or "VG-10," even with typos.

Phase 2: LLM Entity Discovery (OpenRouter)

To find the niche, artisan, or misspelled brands that Fuse.js misses, I use an LLM.

Crucially, I first mask the entities found in Phase 1 (e.g., "I love my [FOUND_ENTITY] gyuto..."). This forces the LLM to focus only on the unknown terms, saving tokens and preventing redundant work.

I send the masked text to a model like Claude or GPT-4 with a specialized "knife expert" prompt, asking it to extract any remaining brands or models. This is how it discovers less common makers like "Shiro Kamo" or "Yoshikane."

Phase 3 & 4: Sentiment & Summarization (LLM)

With a complete list of entities from both phases, I make another LLM call to perform sentiment analysis on each one, scoring them from -1.0 (negative) to +1.0 (positive).

The system also generates a summary of the entire Reddit thread and calculates a "controversy score" based on sentiment variance.

Phase 5: Storage (MongoDB)

Finally, all the extracted mentions, aggregated entities, sentiment scores, and summaries are saved to MongoDB for analysis.

So, What's the Best Chef Knife According to Reddit? The data reveals some interesting trends:

Most Mentioned: Tojiro, Victorinox, and Takamura are the most frequently discussed brands, often recommended for their value.

Most Loved (Best Positive-to-Negative Ratio): This is a better metric for quality. The clear winners are Japanese artisan brands. Shiro Kamo had a stunning 58 positive mentions for every 1 negative. Fujitora and Masutani also had overwhelmingly positive feedback.

Most Controversial: Shun is the most polarizing brand by far, with a high number of both very positive and very negative reviews. Dalstrong had the worst overall sentiment, with more negative mentions than positive.

One of the biggest challenges was handling the long tail of niche entities. Using Fuse.js alone missed too much, and using an LLM for everything was too slow and expensive. The hybrid two-pass approach provided the best of both worlds.

I wrote a more detailed article about the architecture and findings here: https://new.knife.day/blog/reddit-chef-knives-sentiment-analysis

and more technical details of the analysis can be found here: https://github.com/pvijeh/reddit-named-entity-recognition/blob/main/chefknives-brands.md

Happy to answer any questions. Thanks for checking it out!

Discussion 0 comments · 3 points · p-s-v · 2025-10-19
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com.

    About YAVCHN

    YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

    Created by Paul Parks and built with PUDL.

    YAVCHN source code on GitHub

    Help

    Keyboard

    j / k
    Move down and up the story list. The arrow keys scroll whatever has focus.
    Enter
    Read the marked story in the article reader.
    ]
    Read the next story in the same article-reader applet. Back returns to the previous story.
    p
    Pin or unpin the marked story, which keeps it in Pinned.
    n / N
    Move to the next or previous top-level comment in the window in front.
    c
    Collapse or expand that comment.
    f
    Hide or show the story list.
    Esc
    Close a menu or this help.
    Access key m
    Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
    ?
    Show this help.

    Windows

    Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Next story link reads on down the list in the same window.

    A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

    While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

    The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

    The list

    The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

    Browsing view

    View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page and Open in a window are one-off actions that do not change your saved default. Direct page links always open as pages.

    Applets

    The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

    They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser.

    Find

    Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

    About

    YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Pins, hidden stories, filters and layout are kept in this browser only.

    Open source: github.com/paulmooreparks/yavchn. Built with PUDL.