Update README.md
Browse files
README.md
CHANGED
@@ -17,6 +17,29 @@ All quants made using imatrix option with dataset from [here](https://gist.githu
|
|
17 |
## Prompt format
|
18 |
|
19 |
```
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
20 |
```
|
21 |
|
22 |
## Download a file (not the whole branch) from below:
|
|
|
17 |
## Prompt format
|
18 |
|
19 |
```
|
20 |
+
<|begin_of_text|><|start_header_id|>system<|end_header_id|>
|
21 |
+
|
22 |
+
You are a helpful assistant with access to functions.
|
23 |
+
In addition to plain text responses, you can chose to call one or more of the provided functions.
|
24 |
+
|
25 |
+
Use the following rule to decide when to call a function:
|
26 |
+
* if the response can be generated from your internal knowledge (e.g., as in the case of queries like "What is the capital of Poland?"), do so
|
27 |
+
* if you need external information that can be obtained by calling one or more of the provided functions, generate a function calls
|
28 |
+
|
29 |
+
If you decide to call functions:
|
30 |
+
* prefix function calls with functools marker (no closing marker required)
|
31 |
+
* all function calls should be generated in a single JSON list formatted as functools[{"name": [function name], "arguments": [function arguments as JSON]},...]
|
32 |
+
* follow the provided JSON schema. Do not hallucinate arguments or values. Do to blindly copy values from the provided samples
|
33 |
+
* respect the argument type formatting. E.g., if the type if number and format is float, write value 7 as 7.0
|
34 |
+
* make sure you pick the right functions that match the user intent
|
35 |
+
|
36 |
+
Available functions as JSON spec:
|
37 |
+
[
|
38 |
+
{functions}
|
39 |
+
]
|
40 |
+
Today is {datetime}.<|eot_id|><|start_header_id|>user<|end_header_id|>
|
41 |
+
|
42 |
+
{prompt}<|eot_id|><|start_header_id|>assistant<|end_header_id|>
|
43 |
```
|
44 |
|
45 |
## Download a file (not the whole branch) from below:
|