Hacker News

Top stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. Hister: A private search engine for the pages you visit and the files you keep(github.com/asciimoo ↗)
    60comments
  2. Fujitsu launches made-in-Japan next-generation CPU FUJITSU-MONAKA(global.fujitsu ↗)
    146comments
  3. CrowdSec Source Code Leak(crowdsec.net ↗)
    25comments
  4. Rate limits on GitLab.com are changing(about.gitlab.com ↗)
    87comments
  5. Towards Self-Driving Codebases(detail.dev ↗)
    22comments
  6. Why I didn’t sign the Fields medallists’ letter(gowers.wordpress.com ↗)
    174comments
  7. Infinite-Parameter LLMs: Generating and Adapting Weights from Live Data(arxiv.org ↗)
    8comments
  8. How GLM built its own inference infrastructure(z.ai ↗)
    229comments
  9. One year of sponsored Servo development(servo.org ↗)
    128comments
  10. Zettascale (YC S24) Is Hiring ASIC/FPGA Engineers to Build Chips for ASI(zscc.ai ↗)
    discuss
  11. Launch HN: Skillsync (YC W26) – AI chat sessions made portable across agents
    19comments
  12. The American Religion of Self-Storage Facilities(newyorker.com ↗)
    177comments
  13. Running Ubuntu on the Lenovo IdeaPad Duet(vhaudiquet.fr ↗)
    2comments
  14. Grand MS-DOS Gaming General MIDI Showdown(johnnovak.net ↗)
    5comments
  15. Show HN: Share your AI Setup, Learn from others(mysetup.ai ↗)
    70comments
  16. CCC invites all model citizens to 40C3(ccc.de ↗)
    119comments
  17. Show HN: Craigslist for agent skills, curated by a human(skillbay.sh ↗)
    4comments
  18. Ask HN: How to recover Google auth after phone stolen?
    61comments
  19. The Return of Sail Power: Cargo Ships Are Turning Back to the Wind(gcaptain.com ↗)
    102comments
  20. TSMC revealing details about next gen A14 node(mapyourshow.com ↗)
    6comments
  21. Don't Make Job Referrals Public(melashri.net ↗)
    discuss
  22. Whoisinspace.com/(whoisinspace.com ↗)
    56comments
  23. LLM Classification Is Feature Engineering(minimallysufficient.com ↗)
    12comments
  24. My temporary PHP fix from 2014 has nearly 20M installs. Today I'm deprecating it(jakeasmith.com ↗)
    85comments
  25. Stallman: Thousands Dead, Millions Deprived of Liberties (2001)(slashdot.org ↗)
    24comments
  26. Artificial intelligence now beats some of the best human forecasters(economist.com ↗)
    75comments
  27. Economic policy for AGI(deepmind.com ↗)
    18comments
  28. Vinix – A modern operating system written in V(vinix-os.org ↗)
    43comments
  29. Mastering Layout Engines in Graphviz: Dot vs. Neato vs. Twopi vs. Circo(visual-paradigm.com ↗)
    6comments
  30. Keys Not Included: recovering the signing keys for US driver's license barcodes(ryan.science ↗)
    137comments

LLM Classification Is Feature Engineering

59 pointsby 3h agominimallysufficient.com
12 comments
3h agoHN ↗

I don't understand the point they are trying to make.

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.

3h agoHN ↗

I took the point as: don't make the LLM the classifier. Use it to turn messy input into useful features, then let a normal model make the actual decision. That gives you thresholds/calibration you can inspect.

What I'm not sure about is how stable those features are when you switch the underlying LLM or model version.

1h agoHN ↗

Much like how you shouldn't ask the LLM to solve a (repeated, logical) problem, but you should instead prompt it to generate code that you can inspect/test/fix/reuse.

2h agoHN ↗

Why does he first ask to label "ironic" or "not", and then answer the feature questions? Wouldn't it be better to reverse the order?

2h agoHN ↗

Why not use a text embedder for the unstructured data and concatenate with the structured data?

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?

2h agoHN ↗

Calibration / Threshold Control

The amount of thinking is relatively calibrated. Ask an obvious classification, you get an instant answer. Ask a tricky one, much more thinking.

2h agoHN ↗

I really wish people would define terms when using math. What is y? What is LLM(x)? Presumably it evaluates to some real number so that it can be fed to the logistic sigmoid function. If it is the logistic function, then why does beta going to infinity matter? It seems to just collapse the output of the sigmoid function to 1 and make the value of LLM(x) meaningless instead of their claim that it recovers the LLM classifier. What is the function I()?

Maybe these are well understood terms in some field? Maybe I'm just lost?

2h agoHN ↗

Really needs a comparison to the "megaprompt" itself (i.e. "here is a tweet, rate it as ironic or not, considering the following properties; explain your reasoning then output your final answer at the end"). I bet that would get you very far towards the logistic classifier, and would generalize much better out of distribution.

1h agoHN ↗

You can also get LLM to optimize rules for a rules engine iteratively against some dataset.

It’s sort of like memoizing or distilling the knowledge. Works really well for certain type of problems.

17m agoHN ↗

I think that this can be automated by using two LLMs: a stronger/more expensive for generating prompts and a weaker for actual classification. Approximate algorithm:

1. Give "strong" LLM the task formulation and some labeled examples. Ask it to generate a prompt for the "weak" LLM.

2. Run "weak" LLM on the training set with generated prompt from 1, use replies as features for a smaller ML model (logreg, decision tree etc).

3. Pick examples from the training set that your small model is most wrong about and ask "strong" LLM to generate one more prompt (like in 1), except this time you are using the misclassified examples instead of random.

4. Run "weak" LLM on generated prompt from 3, add results as one more feature for your model.

5. Repeat 2 - 4 until your token budget for this task is exhausted or required score on cross validation set is reached.

I was thinking about creating an open source library that implements this, but I'm not sure if anyone really needs it. I suspect that people who need something like this already made their own implementation.