Live data from Hacker News

Optimizing LLMs from a Dataset Perspective

sebastianraschka.com

11–20 of 26 posts

Re: Optimizing LLMs from a Dataset Perspective

#11
post #7

What are other than fine-tuning methods to make LLM smarter? Im familair with RAG - Retrival Augumented Generation.

RLHF is a popular candidate, but the focus is more on "helpfulness" and "safety" -- I don't think it necessarily improves LLMs on reasoning benchmarks

if anything, RLHF makes the model dumber, not smarter.

Re: Optimizing LLMs from a Dataset Perspective

#12
post #7

Earlier quoted context omitted.

RLHF is a popular candidate, but the focus is more on "helpfulness" and "safety" -- I don't think it necessarily improves LLMs on reasoning benchmarks

if anything, RLHF makes the model dumber, not smarter.

I think it could potentially make the model smarter, but it's up to how you collect the data to train the reward models. Currently, companies & papers that use RLHF focus on "safety" rankings, for example. But you could potentially collect labels "smartness" or "correctness" instead and train the the reward model one these. (And then use that reward model to finetune the LLM you want to improve.)

Re: Optimizing LLMs from a Dataset Perspective

#14

What are other than fine-tuning methods to make LLM smarter? Im familair with RAG - Retrival Augumented Generation.

Other than fine-tuning and RAG, Guidance allows you to constrain the output of an LLM within a grammar, for example to guarantee JSON output 100% of the time.

Here's one library to do this https://github.com/guidance-ai/guidance

Re: Optimizing LLMs from a Dataset Perspective

#15
post #9

I have wondered if the very big models trained on a Big Pile of Everything can be used to curate smaller, higher quality data sets that lead to high performing models with smaller parameter counts. Not only are smaller models easier to distribute and faster at inference time, but it offers a licensing escape hatch if future copyright law changes or court rulings make it hard to publicly offer models trained on non-pe…

Not sure on the licensing but yes you can do that technically. Phi-1 and therefore phi-1.5 are partially trained on gpt3.5 generated synthetic textbooks.

The premise here is specifically not to train it on generated output of the bigger model but to merely use the bigger model to better curate non-generated (and thereby untainted) inputs for the training set of the smaller model.

Re: Optimizing LLMs from a Dataset Perspective

#16

I have wondered if the very big models trained on a Big Pile of Everything can be used to curate smaller, higher quality data sets that lead to high performing models with smaller parameter counts. Not only are smaller models easier to distribute and faster at inference time, but it offers a licensing escape hatch if future copyright law changes or court rulings make it hard to publicly offer models trained on non-pe…

Doesn't that lead to model collapse?

Re: Optimizing LLMs from a Dataset Perspective

#17
post #16

I have wondered if the very big models trained on a Big Pile of Everything can be used to curate smaller, higher quality data sets that lead to high performing models with smaller parameter counts. Not only are smaller models easier to distribute and faster at inference time, but it offers a licensing escape hatch if future copyright law changes or court rulings make it hard to publicly offer models trained on non-pe…

Doesn't that lead to model collapse?

The trick is training a little, then augmenting with documents using RAG. The idea that a model alone can handle complex use cases is common, but usually wrong.

Re: Optimizing LLMs from a Dataset Perspective

#18
post #2

I was hoping that this would go more into the details of dataset selection and what makes for high-quality data, but it seems to be more a prelude to a Lit-GPT advertisement :/

I speculate high quality data can be compared to be similar via embeddings comparisons. By organizing the dataset using features, grouping the vectors by them, and ensuring the dataset relates to itself in a given domain by quality tags, we can speculate the data becomes better as we are more specific with our queries to it.

I need to train more models to see if this is an accurate claim, but I've been finishing up the storage layer and haven't gotten to that yet.

Re: Optimizing LLMs from a Dataset Perspective

#19

What are other than fine-tuning methods to make LLM smarter? Im familair with RAG - Retrival Augumented Generation.

Ensembles, for one. We might ask the same question of keyword extraction, for example, and then aggregate the results. Here's a horrible example, but it works and runs on a GPU box: https://github.com/FeatureBaseDB/Laminoid/blob/main/sloth/sl...

Keyterms can be used in the prompt to drive the LLM to better grounded responses as well as helping locate relevant embeddings for RAG, when vector search isn't enough.

Another consideration is writing code for processing things that look similar. For example, one might have the LLM write regex code which is then tested to work and put into production in a pipeline to parse log files, or write SQL off conversational queries, which are then run against a database.

Re: Optimizing LLMs from a Dataset Perspective

#20

What would a good fine-tuning dataset for language translation look like? I want to try fine-tuning to machine translate to and from a fairly niche language ( https://en.wikipedia.org/wiki/S'gaw_Karen_language) . How much text would I need, and what format would be ideal? I have a number of book length texts, most only in the target language, and a few bilingual or multilingual. For the bilingual and multilingual tex…

If you want to fine tune Llama 2 or similar, then embed each pair together and separately and store them. Then, use the unlabeled data (the source text without translation) to query the embeddings for similar matches. You then send in the necessary prompt text with the matches, plus the text to translate. You'll want to do this with a foundational model, like GPT-x.

As noted below, extracting words or keyterms would maybe be a good idea, as they could be included in the training set.

The training set would the be comprised of the prompt, the translation, and keyterms. As you will want to vet the generated texts anyway, you could then decide if the foundational model was working enough. You could also try to run the largest "open" model you could find on the prompts, to see if those needed training as well. There are many different Llama models trained on HuggingFace for language pairs, so see if your languages are already built and test those.

I'm building a simple, Open Source ML pipeline manager at https://ai.featurebase.com/. I'd be down to help you with this!

Post reply on HN