I’m using gpt-3.5-turbo-1106 and the chat.completions.create endpoint to write short programming how-to’s. It’s doing an amazing job for the most part.
I realize that writing quality is somewhat subjective. With that in mind, I’d like to eliminate this kind of content from responses.
These examples demonstrate different ways to convert a date into a string using Bash. You can choose the method that best suits your requirements.
By using these methods, you can effectively concatenate strings in Bash for various scripting and programming tasks.
By following these examples, you can easily obtain the current date in your Elixir programs.
Meta: references to the prompt
(Occasionally present)
I hope this meets your requirements. If you need any further help, feel free to ask!
Sure, I can help with that. Here is the article:
Title: Getting the Current Date in Elixir
I believe that gpt-4-* might do better. But I’d (of course) like to stay with the less expensive gpt-3.5-* if I can. Especially since 2021 data is fine for this use case.
I also haven’t tried the JSON-response format. Would it enable more specific requests that could eliminate the fluff?
Doesn’t answer your question, but here’s an opinion:
This is purely subjective, but I like what you call meta fluff, especially for generation.
I like to try to elicit a maximally positive reaction to the prompt, and allow the model to waffle on a bit before getting to the meat of it, and then extract the actual product through other means (e.g. asking the model to include delimiters, or using a weaker model to transcribe the content)
So I’m going to try asking for a JSON response with the parts of the article broken out—intro, examples, conclusion. And maybe get more predictable responses.
You could also send the first response you got from GPT3 back into GPT3 with some type of prompt that request it to simply summarize the facts or strip out non-essential statements. Doing a second pass might further improve the quality of the result as well.