Do 2B models have practical use cases, or are they just toys for now?

We didn't just accept the raw output from the LLM and slap it into the DB as the new value, that feels like what people are assuming here. I'll give a bit more detail here since it was a pretty fun project: The goal was to take a `Name` column from an old system that contained either a business's name or a person's full name (there was no discriminator field) and fill in either a `BusinessName` or `FirstName` and `LastName` along with a discriminator field in the new DB. We're talking over 100,000 records that were all just "accounts" and now needed to be either a "residential" or "business" account with correctly formatted names. The system asked the LLM to generate an object that looked like this: { "account_type: "person" | "business", "business_name": null | <name>, "first_name": null | <first-name>, "last_name": null | <last-name>, "requires_review": true | false, "review_reason": null | <reason> } It was asked to require review if it wasn't sure if the account belonged to a business or a person or if it wasn't sure about formatting of the name. We made a little web app that would display the review-required items and allow someone on the team to quickly fix it. Overall there weren't many errors or required reviews. To also make sure we weren't writing slop to the new DB, there were some validations we performed: 1. Make sure the JSON was well-formed and conformed to our schema. (e.g. both "business\_name" and "first\_name" / "last\_name" can't be filled out as they are mutually exclusive sparse fields). 2. The formatted name would be upper-cased, apostrophes would be removed, and then that would have to match the original database field. A review would be triggered if it didn't match. This happened more times for businesses, sometimes the LLM would would off the "LLC" or minor punctuation like a period in a business name.