Update README.md
Browse files
README.md
CHANGED
|
@@ -1,204 +1,107 @@
|
|
| 1 |
---
|
| 2 |
library_name: peft
|
| 3 |
base_model: mistralai/Mistral-7B-v0.1
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 4 |
---
|
| 5 |
|
| 6 |
-
#
|
| 7 |
|
| 8 |
-
|
|
|
|
|
|
|
| 9 |
|
|
|
|
| 10 |
|
|
|
|
| 11 |
|
| 12 |
-
|
| 13 |
|
| 14 |
-
|
| 15 |
|
| 16 |
-
|
| 17 |
|
|
|
|
| 18 |
|
|
|
|
| 19 |
|
| 20 |
-
|
| 21 |
-
|
| 22 |
-
|
| 23 |
-
|
| 24 |
-
- **Language(s) (NLP):** [More Information Needed]
|
| 25 |
-
- **License:** [More Information Needed]
|
| 26 |
-
- **Finetuned from model [optional]:** [More Information Needed]
|
| 27 |
|
| 28 |
-
|
| 29 |
|
| 30 |
-
|
| 31 |
|
| 32 |
-
|
| 33 |
-
- **Paper [optional]:** [More Information Needed]
|
| 34 |
-
- **Demo [optional]:** [More Information Needed]
|
| 35 |
|
| 36 |
-
|
|
|
|
| 37 |
|
| 38 |
-
|
| 39 |
|
| 40 |
-
|
| 41 |
|
| 42 |
-
|
| 43 |
|
| 44 |
-
|
|
|
|
|
|
|
|
|
|
| 45 |
|
| 46 |
-
|
| 47 |
|
| 48 |
-
|
| 49 |
|
| 50 |
-
|
| 51 |
|
| 52 |
-
|
| 53 |
-
|
| 54 |
-
<!-- This section addresses misuse, malicious use, and uses that the model will not work well for. -->
|
| 55 |
-
|
| 56 |
-
[More Information Needed]
|
| 57 |
-
|
| 58 |
-
## Bias, Risks, and Limitations
|
| 59 |
-
|
| 60 |
-
<!-- This section is meant to convey both technical and sociotechnical limitations. -->
|
| 61 |
-
|
| 62 |
-
[More Information Needed]
|
| 63 |
-
|
| 64 |
-
### Recommendations
|
| 65 |
-
|
| 66 |
-
<!-- This section is meant to convey recommendations with respect to the bias, risk, and technical limitations. -->
|
| 67 |
-
|
| 68 |
-
Users (both direct and downstream) should be made aware of the risks, biases and limitations of the model. More information needed for further recommendations.
|
| 69 |
-
|
| 70 |
-
## How to Get Started with the Model
|
| 71 |
-
|
| 72 |
-
Use the code below to get started with the model.
|
| 73 |
-
|
| 74 |
-
[More Information Needed]
|
| 75 |
-
|
| 76 |
-
## Training Details
|
| 77 |
-
|
| 78 |
-
### Training Data
|
| 79 |
-
|
| 80 |
-
<!-- This should link to a Dataset Card, perhaps with a short stub of information on what the training data is all about as well as documentation related to data pre-processing or additional filtering. -->
|
| 81 |
-
|
| 82 |
-
[More Information Needed]
|
| 83 |
-
|
| 84 |
-
### Training Procedure
|
| 85 |
-
|
| 86 |
-
<!-- This relates heavily to the Technical Specifications. Content here should link to that section when it is relevant to the training procedure. -->
|
| 87 |
-
|
| 88 |
-
#### Preprocessing [optional]
|
| 89 |
-
|
| 90 |
-
[More Information Needed]
|
| 91 |
-
|
| 92 |
-
|
| 93 |
-
#### Training Hyperparameters
|
| 94 |
-
|
| 95 |
-
- **Training regime:** [More Information Needed] <!--fp32, fp16 mixed precision, bf16 mixed precision, bf16 non-mixed precision, fp16 non-mixed precision, fp8 mixed precision -->
|
| 96 |
-
|
| 97 |
-
#### Speeds, Sizes, Times [optional]
|
| 98 |
-
|
| 99 |
-
<!-- This section provides information about throughput, start/end time, checkpoint size if relevant, etc. -->
|
| 100 |
-
|
| 101 |
-
[More Information Needed]
|
| 102 |
-
|
| 103 |
-
## Evaluation
|
| 104 |
-
|
| 105 |
-
<!-- This section describes the evaluation protocols and provides the results. -->
|
| 106 |
-
|
| 107 |
-
### Testing Data, Factors & Metrics
|
| 108 |
-
|
| 109 |
-
#### Testing Data
|
| 110 |
-
|
| 111 |
-
<!-- This should link to a Dataset Card if possible. -->
|
| 112 |
-
|
| 113 |
-
[More Information Needed]
|
| 114 |
-
|
| 115 |
-
#### Factors
|
| 116 |
-
|
| 117 |
-
<!-- These are the things the evaluation is disaggregating by, e.g., subpopulations or domains. -->
|
| 118 |
-
|
| 119 |
-
[More Information Needed]
|
| 120 |
-
|
| 121 |
-
#### Metrics
|
| 122 |
-
|
| 123 |
-
<!-- These are the evaluation metrics being used, ideally with a description of why. -->
|
| 124 |
-
|
| 125 |
-
[More Information Needed]
|
| 126 |
-
|
| 127 |
-
### Results
|
| 128 |
-
|
| 129 |
-
[More Information Needed]
|
| 130 |
-
|
| 131 |
-
#### Summary
|
| 132 |
-
|
| 133 |
-
|
| 134 |
-
|
| 135 |
-
## Model Examination [optional]
|
| 136 |
-
|
| 137 |
-
<!-- Relevant interpretability work for the model goes here -->
|
| 138 |
-
|
| 139 |
-
[More Information Needed]
|
| 140 |
-
|
| 141 |
-
## Environmental Impact
|
| 142 |
-
|
| 143 |
-
<!-- Total emissions (in grams of CO2eq) and additional considerations, such as electricity usage, go here. Edit the suggested text below accordingly -->
|
| 144 |
-
|
| 145 |
-
Carbon emissions can be estimated using the [Machine Learning Impact calculator](https://mlco2.github.io/impact#compute) presented in [Lacoste et al. (2019)](https://arxiv.org/abs/1910.09700).
|
| 146 |
-
|
| 147 |
-
- **Hardware Type:** [More Information Needed]
|
| 148 |
-
- **Hours used:** [More Information Needed]
|
| 149 |
-
- **Cloud Provider:** [More Information Needed]
|
| 150 |
-
- **Compute Region:** [More Information Needed]
|
| 151 |
-
- **Carbon Emitted:** [More Information Needed]
|
| 152 |
-
|
| 153 |
-
## Technical Specifications [optional]
|
| 154 |
-
|
| 155 |
-
### Model Architecture and Objective
|
| 156 |
-
|
| 157 |
-
[More Information Needed]
|
| 158 |
-
|
| 159 |
-
### Compute Infrastructure
|
| 160 |
-
|
| 161 |
-
[More Information Needed]
|
| 162 |
-
|
| 163 |
-
#### Hardware
|
| 164 |
-
|
| 165 |
-
[More Information Needed]
|
| 166 |
-
|
| 167 |
-
#### Software
|
| 168 |
-
|
| 169 |
-
[More Information Needed]
|
| 170 |
-
|
| 171 |
-
## Citation [optional]
|
| 172 |
-
|
| 173 |
-
<!-- If there is a paper or blog post introducing the model, the APA and Bibtex information for that should go in this section. -->
|
| 174 |
-
|
| 175 |
-
**BibTeX:**
|
| 176 |
-
|
| 177 |
-
[More Information Needed]
|
| 178 |
-
|
| 179 |
-
**APA:**
|
| 180 |
-
|
| 181 |
-
[More Information Needed]
|
| 182 |
-
|
| 183 |
-
## Glossary [optional]
|
| 184 |
-
|
| 185 |
-
<!-- If relevant, include terms and calculations in this section that can help readers understand the model or model card. -->
|
| 186 |
-
|
| 187 |
-
[More Information Needed]
|
| 188 |
-
|
| 189 |
-
## More Information [optional]
|
| 190 |
-
|
| 191 |
-
[More Information Needed]
|
| 192 |
-
|
| 193 |
-
## Model Card Authors [optional]
|
| 194 |
-
|
| 195 |
-
[More Information Needed]
|
| 196 |
-
|
| 197 |
-
## Model Card Contact
|
| 198 |
-
|
| 199 |
-
[More Information Needed]
|
| 200 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 201 |
|
| 202 |
### Framework versions
|
| 203 |
|
| 204 |
-
- PEFT 0.8.2
|
|
|
|
|
|
| 1 |
---
|
| 2 |
library_name: peft
|
| 3 |
base_model: mistralai/Mistral-7B-v0.1
|
| 4 |
+
license: apache-2.0
|
| 5 |
+
datasets:
|
| 6 |
+
- bitext/Bitext-customer-support-llm-chatbot-training-dataset
|
| 7 |
+
language:
|
| 8 |
+
- en
|
| 9 |
+
tags:
|
| 10 |
+
- text-generation-inference
|
| 11 |
---
|
| 12 |
|
| 13 |
+
# Description
|
| 14 |
|
| 15 |
+
This LoRA adapter was fine-tuned on the `bitext/Bitext-customer-support-llm-chatbot-training-dataset`, specifically by:
|
| 16 |
+
1. Grouping the data on the following `category` column values: `PAYMENT`, `INVOICE`, `REFUND`
|
| 17 |
+
2. Merging `intent` and `response` columns into a new single column called `response_json` that is a JSON object consistint of two keys: `intent` and `response`.
|
| 18 |
|
| 19 |
+
This is what the dataset looks like once it is preprared:
|
| 20 |
|
| 21 |
+
<img src="./payments_dataset.png" alt="drawing" width="1500"/>
|
| 22 |
|
| 23 |
+
It also has the following token distribution (without the prompt template being merged into the input)
|
| 24 |
|
| 25 |
+
<img src="./token_distribution.png" alt="drawing" width="400"/>
|
| 26 |
|
| 27 |
+
# How To Use This Model
|
| 28 |
|
| 29 |
+
## Prompt Template
|
| 30 |
|
| 31 |
+
This adapter was instruction tuned using the following prompt template:
|
| 32 |
|
| 33 |
+
```text
|
| 34 |
+
You are a support agent for a company and you receive requests from customers.
|
| 35 |
+
Your job is to reply to the customer by providing both the intent, which you
|
| 36 |
+
should determine from the customer's request, as well as an appropriate response.
|
|
|
|
|
|
|
|
|
|
| 37 |
|
| 38 |
+
Please note that the intent can only be one of the following: check_payment_methods, get_invoice, check_refund_policy, track_refund, payment_issue, check_invoice, get_refund.
|
| 39 |
|
| 40 |
+
Please package your reply in the JSON format.
|
| 41 |
|
| 42 |
+
Request: {instruction}
|
|
|
|
|
|
|
| 43 |
|
| 44 |
+
Reply:
|
| 45 |
+
```
|
| 46 |
|
| 47 |
+
At inference time, just replace/insert `{instruction}` with an actual instruction.
|
| 48 |
|
| 49 |
+
## Example Input and Output
|
| 50 |
|
| 51 |
+
Input:
|
| 52 |
|
| 53 |
+
```
|
| 54 |
+
You are a support agent for a company and you receive requests from customers.
|
| 55 |
+
Your job is to reply to the customer by providing both the intent, which you
|
| 56 |
+
should determine from the customer's request, as well as an appropriate response.
|
| 57 |
|
| 58 |
+
Please note that the intent can only be one of the following: check_payment_methods, get_invoice, check_refund_policy, track_refund, payment_issue, check_invoice, get_refund.
|
| 59 |
|
| 60 |
+
Please package your reply in the JSON format.
|
| 61 |
|
| 62 |
+
Request: can you help me check in which cases can I ask for refunds?
|
| 63 |
|
| 64 |
+
Reply:
|
| 65 |
+
```
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 66 |
|
| 67 |
+
Output (rendered using pprint, but is a proper JSON with full key-value pairs):
|
| 68 |
+
```python
|
| 69 |
+
{'intent': 'check_refund_policy',
|
| 70 |
+
'response': "I'll do my best! I completely understand your need to have a "
|
| 71 |
+
'clear understanding of the situations in which you can request a '
|
| 72 |
+
'refund. Let me provide you with a comprehensive breakdown:\n'
|
| 73 |
+
'\n'
|
| 74 |
+
'1. **Product/Service Defect:** If the product or service you '
|
| 75 |
+
"purchased has a defect or doesn't meet the description, you are "
|
| 76 |
+
'typically eligible for a refund.\n'
|
| 77 |
+
'2. **Cancellation within Grace Period:** Should you change your '
|
| 78 |
+
'mind and decide to cancel your purchase within the specified '
|
| 79 |
+
'grace period, you should be able to receive a refund.\n'
|
| 80 |
+
'3. **Unauthorized Charges:** If you notice any charges on your '
|
| 81 |
+
"account that you didn't authorize or recognize, we will "
|
| 82 |
+
'investigate the matter and assist you in obtaining a refund.\n'
|
| 83 |
+
'4. **Event Cancellation:** If you purchased tickets for an event '
|
| 84 |
+
'that gets canceled without a rescheduled date, you would usually '
|
| 85 |
+
'be entitled to a refund.\n'
|
| 86 |
+
'5. **Duplicate Charges:** If you have been charged multiple '
|
| 87 |
+
'times for the same item, please inform us, and we will rectify '
|
| 88 |
+
'the situation promptly.\n'
|
| 89 |
+
"6. **Non-receipt of Goods:** If you haven't received your "
|
| 90 |
+
'ordered product within the expected timeframe, you may qualify '
|
| 91 |
+
'for a refund.\n'
|
| 92 |
+
'\n'
|
| 93 |
+
'Please keep in mind that refund policies may vary depending on '
|
| 94 |
+
"the vendor or service provider. It's always a good idea to "
|
| 95 |
+
'review their terms and conditions or contact them directly for '
|
| 96 |
+
'more specific information. If you have any specific concerns or '
|
| 97 |
+
'need assistance with a particular order, please provide me with '
|
| 98 |
+
"the necessary details, such as the order number, and I'll be "
|
| 99 |
+
'glad to assist you further.\n'
|
| 100 |
+
'\n'
|
| 101 |
+
'Is there anything else I can help you with today?'}
|
| 102 |
+
```
|
| 103 |
|
| 104 |
### Framework versions
|
| 105 |
|
| 106 |
+
- PEFT 0.8.2
|
| 107 |
+
- Ludwig 0.10.2
|