Update README.md
Browse files
README.md
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
-
---
|
| 2 |
-
license: apache-2.0
|
| 3 |
-
task_categories:
|
| 4 |
-
- text-generation
|
| 5 |
-
language:
|
| 6 |
-
- en
|
| 7 |
-
size_categories:
|
| 8 |
-
- n<1K
|
| 9 |
-
---
|
| 10 |
# Preparing Your Dataset
|
| 11 |
|
| 12 |
Once you’ve decided that fine-tuning is the best approach—after optimizing your prompt as much as possible and identifying remaining model issues—you’ll need to prepare training data. Start by creating a diverse set of example conversations that mirror those the model will handle during production.
|
|
@@ -57,7 +57,7 @@ Each example should follow this structure below, consisting of a list of message
|
|
| 57 |
- `parameters` (dict): An object that defines the inputs required by the tool
|
| 58 |
- `type` (str): Specifies the expected type of the parameters. For this tool, the type is `object`, meaning structured data is required.
|
| 59 |
- `properties` (dict): Describes the attributes the tool can accept, where each key represents a specific input parameter.
|
| 60 |
-
- `required` (list): Specifies which parameters are mandatory.
|
| 61 |
|
| 62 |
```json
|
| 63 |
[
|
|
|
|
| 1 |
+
---
|
| 2 |
+
license: apache-2.0
|
| 3 |
+
task_categories:
|
| 4 |
+
- text-generation
|
| 5 |
+
language:
|
| 6 |
+
- en
|
| 7 |
+
size_categories:
|
| 8 |
+
- n<1K
|
| 9 |
+
---
|
| 10 |
# Preparing Your Dataset
|
| 11 |
|
| 12 |
Once you’ve decided that fine-tuning is the best approach—after optimizing your prompt as much as possible and identifying remaining model issues—you’ll need to prepare training data. Start by creating a diverse set of example conversations that mirror those the model will handle during production.
|
|
|
|
| 57 |
- `parameters` (dict): An object that defines the inputs required by the tool
|
| 58 |
- `type` (str): Specifies the expected type of the parameters. For this tool, the type is `object`, meaning structured data is required.
|
| 59 |
- `properties` (dict): Describes the attributes the tool can accept, where each key represents a specific input parameter.
|
| 60 |
+
- `required` Optional (list): Specifies which parameters are mandatory.
|
| 61 |
|
| 62 |
```json
|
| 63 |
[
|