This node allows you to fine-tune an OpenAI Chat Model based on a conversation table.
The fine-tuning data needs to be in the following format and contain at least 10 conversations, each of which must contain at least one system message:
ID | Role | Content |
1 | system | You are a happy assistant that puts a positive spin on everything. |
1 | user | I lost my tennis match today. |
1 | assistant | It's ok, it happens to everyone. |
2 | user | I lost my book today. |
2 | assistant | You can read everything on ebooks these days! |
id_string | system | You are a happy assistant that puts a positive spin on everything. |
id_string | assistant | You're great! |
For a training file with 100,000 tokens trained over 3 epochs, the expected cost would be ~$2.40 USD. For more information, visit OpenAI
Column containing references to group rows into conversations.
Column containing the message role. Can be either 'system', 'assistant' or 'user'.
Column containing the message contents.
An epoch refers to one full cycle through the training dataset. If set to 'Auto', OpenAI will determine a reasonable value.
Available options:
An epoch refers to one full cycle through the training dataset.
A larger batch size means that model parameters are updated less frequently, but with lower variance. If set to 'Auto', OpenAI will determine a reasonable value.
Available options:
A larger batch size means that model parameters are updated less frequently, but with lower variance.
A smaller learning rate may be useful to avoid overfitting. If set to 'Auto', OpenAI will determine a reasonable value.
Available options:
A smaller learning rate may be useful to avoid overfitting.
A string of up to 18 characters that will be added to your fine-tuned model name.
The time interval in seconds in which the node will check the progress of the fine-tuning job.
Configured OpenAI Chat Model which supports fine-tuning.
The data should be presented across 3 columns:
One column specifying a conversation ID, one representing the role of a message (system, assistant and user), and the third for the content of the message.
The table has to include at least 10 conversations, each of which must contain at least one system message.
You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.
To use this node in KNIME, install the extension KNIME Python Extension Development (Labs) from the below update site following our NodePit Product and Node Installation Guide:
A zipped version of the software site can be downloaded here.
Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.
Try NodePit Runner!Do you have feedback, questions, comments about NodePit, want to support this platform, or want your own nodes or workflows listed here as well? Do you think, the search results could be improved or something is missing? Then please get in touch! Alternatively, you can send us an email to mail@nodepit.com.
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.