LLM Classification Is Feature Engineering(minimallysufficient.com) |
LLM Classification Is Feature Engineering(minimallysufficient.com) |
https://softwaredoug.com/blog/2025/01/21/llm-judge-decision-...
For example you could freeze most of the layers of the embedder but let the final ones learn. Then you wouldn’t need to do either feature or prompt engineering?
It’s sort of like memoizing or distilling the knowledge. Works really well for certain type of problems.
Maybe these are well understood terms in some field? Maybe I'm just lost?
It's very often (always?) the case that something general also solves particular problems.
A sorting algorithm is an implementation of min()
A parser also is a syntax checker.
A route planner is a reachability checker.
A computer algebra system is a basic arithmetic calculator.
A general constraint solver is a Soduku hint maker.
It's true that LLM output can be used as an input to another classifier, this is also true of any classifier. The improvement on top of the straight LLM classification is relatively small, and I would argue that working on the prompt or just including in the prompt for the LLM what features might be useful to consider would likely work even better.Fundamentally I read this article as: We want to build a simpler, dumbed down clone of Mathematica, so we cobbled together the following pieces... We also needed a way to do arithmetic, so we also include a copy of Mathematica to do basic arithmetic.
What I'm not sure about is how stable those features are when you switch the underlying LLM or model version.
The amount of thinking is relatively calibrated. Ask an obvious classification, you get an instant answer. Ask a tricky one, much more thinking.