Netta1994 commited on
Commit
e2411e7
1 Parent(s): e78534c

Add SetFit model

Browse files
1_Pooling/config.json ADDED
@@ -0,0 +1,10 @@
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "word_embedding_dimension": 768,
3
+ "pooling_mode_cls_token": true,
4
+ "pooling_mode_mean_tokens": false,
5
+ "pooling_mode_max_tokens": false,
6
+ "pooling_mode_mean_sqrt_len_tokens": false,
7
+ "pooling_mode_weightedmean_tokens": false,
8
+ "pooling_mode_lasttoken": false,
9
+ "include_prompt": true
10
+ }
README.md ADDED
@@ -0,0 +1,290 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ ---
2
+ base_model: BAAI/bge-base-en-v1.5
3
+ library_name: setfit
4
+ metrics:
5
+ - accuracy
6
+ pipeline_tag: text-classification
7
+ tags:
8
+ - setfit
9
+ - sentence-transformers
10
+ - text-classification
11
+ - generated_from_setfit_trainer
12
+ widget:
13
+ - text: "Evaluation:\n\n1. **Context Grounding**: The answer references the document,\
14
+ \ but it consists of multiple points that are not directly related to accessing\
15
+ \ training resources. While some methods mentioned might facilitate training (e.g.,\
16
+ \ learning budget), others (like using 1Password, Tresorit) are not directly relevant\
17
+ \ to accessing training resources.\n \n2. **Relevance**: The answer partially\
18
+ \ addresses the question. Points about accessing documents or requesting a learning\
19
+ \ budget are somewhat related, but the inclusion of security tools and password\
20
+ \ managers is irrelevant to the question of accessing training resources.\n\n\
21
+ 3. **Conciseness**: The answer includes unnecessary details that do not directly\
22
+ \ answer the question, making it lengthy and off-point in segments.\n\n4. **Specificity**:\
23
+ \ The answer is a mix of specific steps and unrelated information. It fails to\
24
+ \ provide a direct method to access training resources comprehensively.\n\n5.\
25
+ \ **General Tips**: The answer does provide a step about talking to a lead for\
26
+ \ a learning budget, which can be considered a relevant tip. However, it's buried\
27
+ \ in a lot of unrelated content.\n\nOverall, the answer deviates too much from\
28
+ \ the specific question about accessing training resources and includes information\
29
+ \ not requested nor directly relevant.\n\nFinal result: **Bad**"
30
+ - text: 'Evaluation:
31
+
32
+ The answer provided is concise and directly addresses the question of whom to
33
+ contact for travel reimbursement questions. It correctly refers to the email address
34
+ provided in the document. The answer is well-supported by the document and does
35
+ not deviate into unrelated topics.
36
+
37
+
38
+ The final evaluation: Good'
39
+ - text: 'Reasoning:
40
+
41
+
42
+ 1. **Context Grounding**: The answer accurately references content from the provided
43
+ documents, especially the points related to actively thinking about the possibility
44
+ of someone leaving, flagging it to HR, analyzing problems, and providing feedback.
45
+
46
+
47
+ 2. **Relevance**: The answer directly addresses the question by outlining why
48
+ it is crucial for team leads to consider the possibility of staff leaving and
49
+ the steps they can take to mitigate issues early on.
50
+
51
+
52
+ 3. **Conciseness**: The answer is relatively concise but gets slightly verbose
53
+ towards the end. The core points are clearly made without too much unnecessary
54
+ information.
55
+
56
+
57
+ 4. **Specificity**: The answer includes specific reasons like addressing underperformance,
58
+ lack of growth, disagreement with direction, and maintaining a supportive environment,
59
+ all of which are well-supported by the documents.
60
+
61
+
62
+ 5. **Avoiding Generality**: The answer provides detailed steps and reasons as
63
+ mentioned in the documents, avoiding overly general statements.
64
+
65
+
66
+ Final Result: **Good**'
67
+ - text: 'Evaluation:
68
+
69
+ The answer addresses the question partially by suggesting ways to learn about
70
+ ORGANIZATION through their website and available job postings, which are referenced
71
+ in the documents. However, it misses more specific ways to understand their products
72
+ and challenges; for example, details from the document about stress management,
73
+ inclusivity issues, and organizational changes could provide better insights into
74
+ their future and challenges. Additionally, a newsletter about "behind the scenes"
75
+ is more about updates rather than specific details on products and challenges.
76
+ Therefore, the answer lacks completeness and specificity.
77
+
78
+
79
+ The final evaluation: Bad'
80
+ - text: "**Evaluation Reasoning:**\n\n1. **Context Grounding:** The answer is well-supported\
81
+ \ by the provided documents, especially Document 1. It correctly identifies the\
82
+ \ responsibilities of ORGANIZATION_2, Thomas Barnes, and Charlotte Herrera.\n\
83
+ \ \n2. **Relevance:** The answer addresses the specific question about the role\
84
+ \ of ORGANIZATION_2 in the farewell process.\n \n3. **Conciseness:** The response\
85
+ \ includes some redundant information, especially the repetition of individuals\
86
+ \ involved and some operational details not directly related to the extent of\
87
+ \ ORGANIZATION_2's involvement.\n \n4. **Specificity:** It clearly outlines\
88
+ \ the roles and describes the process for different situations, including handling\
89
+ \ paperwork, process, and tough conversations.\n \n5. **General vs. Specific\
90
+ \ Tips:** The answer could have been more concise regarding the involvement extent\
91
+ \ but remains within bounds.\n\n**Final Evaluation: Good**"
92
+ inference: true
93
+ model-index:
94
+ - name: SetFit with BAAI/bge-base-en-v1.5
95
+ results:
96
+ - task:
97
+ type: text-classification
98
+ name: Text Classification
99
+ dataset:
100
+ name: Unknown
101
+ type: unknown
102
+ split: test
103
+ metrics:
104
+ - type: accuracy
105
+ value: 0.6119402985074627
106
+ name: Accuracy
107
+ ---
108
+
109
+ # SetFit with BAAI/bge-base-en-v1.5
110
+
111
+ This is a [SetFit](https://github.com/huggingface/setfit) model that can be used for Text Classification. This SetFit model uses [BAAI/bge-base-en-v1.5](https://huggingface.co/BAAI/bge-base-en-v1.5) as the Sentence Transformer embedding model. A [LogisticRegression](https://scikit-learn.org/stable/modules/generated/sklearn.linear_model.LogisticRegression.html) instance is used for classification.
112
+
113
+ The model has been trained using an efficient few-shot learning technique that involves:
114
+
115
+ 1. Fine-tuning a [Sentence Transformer](https://www.sbert.net) with contrastive learning.
116
+ 2. Training a classification head with features from the fine-tuned Sentence Transformer.
117
+
118
+ ## Model Details
119
+
120
+ ### Model Description
121
+ - **Model Type:** SetFit
122
+ - **Sentence Transformer body:** [BAAI/bge-base-en-v1.5](https://huggingface.co/BAAI/bge-base-en-v1.5)
123
+ - **Classification head:** a [LogisticRegression](https://scikit-learn.org/stable/modules/generated/sklearn.linear_model.LogisticRegression.html) instance
124
+ - **Maximum Sequence Length:** 512 tokens
125
+ - **Number of Classes:** 2 classes
126
+ <!-- - **Training Dataset:** [Unknown](https://huggingface.co/datasets/unknown) -->
127
+ <!-- - **Language:** Unknown -->
128
+ <!-- - **License:** Unknown -->
129
+
130
+ ### Model Sources
131
+
132
+ - **Repository:** [SetFit on GitHub](https://github.com/huggingface/setfit)
133
+ - **Paper:** [Efficient Few-Shot Learning Without Prompts](https://arxiv.org/abs/2209.11055)
134
+ - **Blogpost:** [SetFit: Efficient Few-Shot Learning Without Prompts](https://huggingface.co/blog/setfit)
135
+
136
+ ### Model Labels
137
+ | Label | Examples |
138
+ |:------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
139
+ | 0 | <ul><li>"Evaluation:\nThe answer is too general and lacks specificity regarding the organization's guidelines and criteria for spending money wisely. The provided documents are focused on the study and learning budget within the organization, and the answer should have included aspects such as considering whether an expenditure is a good investment, its alignment with personal and organizational goals, and the outlined budget guidelines.\n\n1. **Context Grounding:** The answer does touch upon wise spending and investments, but it lacks direct references to the specific criteria and guidelines outlined in the documents.\n2. **Relevance:** The answer is somewhat relevant but doesn't delve into the detailed criteria provided about spending the budget wisely.\n3. **Conciseness:** The answer is concise but misses key specifics from the document.\n4. **Avoiding unanswerable responses:** The question could be answered based on the document, and the answer does attempt to respond appropriately.\n5. **Specificity and details:** The answer misses details such as the control questions about personal and organizational benefits, the role and responsibility match, and the specific budget thresholds for various spending categories.\n\nFinal evaluation: Bad"</li><li>'Evaluation:\n\n1. **Context Grounding:** The answer is somewhat grounded in the context provided by the documents but not entirely accurate as it contains errors such as repeated names and unclear sentences.\n2. **Relevance:** The answer does address the question by listing pet peeves, yet it includes unnecessary names and errors that detract from its clarity.\n3. **Conciseness:** The response is not concise and includes redundant information, such as repeated names and irrelevant phrases.\n4. **Clarity:** The answer is marred by text errors (e.g., "Cassandra Rivera Heather Nelson"), which obscure its clarity and readability.\n5. **Specificity:** It does list specific pet peeves mentioned in the document but lacks proper structure and clarity.\n\nFinal evaluation: Bad'</li><li>'The provided answer is inadequate for several reasons:\n\n1. **Context Grounding**: The answer makes vague references to multiple unrelated sections, rather than directly addressing how to access training resources. The mentioned documents do not collectively substantiate the response about accessing training resources.\n\n2. **Relevance**: The instructions involve details about reimbursement, security practices, and learning budgets, but they do not respond directly to the query about accessing training resources.\n\n3. **Conciseness**: The answer includes numerous irrelevant points such as the use of 1Password for personal account management and feedback processing, which are not pertinent to accessing training resources.\n\n4. **Specificity**: The answer does not provide specific steps or tips directly related to accessing the training resources of the company. It rather diverts into various other topics.\n\n5. **Following Instructions**: The given documents offer information about other aspects of work at the company but lack direct guidance on accessing training resources. Thus, attempting to answer the question without appropriate grounding in the document misleads the response.\n\nTherefore, the answer fails to meet the necessary criteria and should be evaluated as:\n\n**Bad**'</li></ul> |
140
+ | 1 | <ul><li>'Evaluation:\nThe provided answer addresses the specific question of how feedback should be given according to the provided tips. It covers key points from the document such as giving feedback at the time of the event, making it situational rather than personal, reflecting on the intention of the feedback, being clear and direct, and showing appreciation. Additionally, it touches on tips for receiving feedback, aligning well with the original document.\n\nHowever, the answer includes erroneous and irrelevant information due to text misanalyzation such as "Christopher Estes time" which should not be part of the answer. Furthermore, the mention of "emichelle James Johnson MDamples" appears to be a corrupted text which doesn’t make sense in the context.\n\nFinal evaluation: Bad'</li><li>'Evaluation:\nThe answer accurately addresses the question of why it is important to proactively share information from high-level meetings. It discusses transparency, alignment, sense of purpose, and open communication, which are all points grounded in the provided documents. The answer is relevant, concise, and specific enough, capturing the essence of the reasons mentioned in Document 4. No irrelevant information is included, and the answer contains specific tips related to the importance of sharing high-level meeting details.\n\nFinal evaluation: Good'</li><li>'Evaluation:\nThe provided answer is generally well-grounded in the document, sticking closely to the instructions given for reporting car travel expenses for reimbursement. However, there are a few inaccuracies and incomplete information:\n\n1. **Context Grounding**: The answer is largely based on the content of the document but not entirely accurate. The provided email addresses seem to be incorrectly formatted (e.g., "finance@Dustin [email protected]" should probably be "[email protected]@example.net").\n2. **Relevance**: The response is relevant to the question asked and sticks to the specific procedure for car travel expense reporting.\n3. **Conciseness**: The answer is concise but could be more accurate in presenting the information.\n4. **Specificity**: The document also mentions tracking kilometers and the reimbursement rate, which the answer includes. However, it fails to mention all the specific details accurately.\n\nFinal evaluation: Bad'</li></ul> |
141
+
142
+ ## Evaluation
143
+
144
+ ### Metrics
145
+ | Label | Accuracy |
146
+ |:--------|:---------|
147
+ | **all** | 0.6119 |
148
+
149
+ ## Uses
150
+
151
+ ### Direct Use for Inference
152
+
153
+ First install the SetFit library:
154
+
155
+ ```bash
156
+ pip install setfit
157
+ ```
158
+
159
+ Then you can load this model and run inference.
160
+
161
+ ```python
162
+ from setfit import SetFitModel
163
+
164
+ # Download from the 🤗 Hub
165
+ model = SetFitModel.from_pretrained("Netta1994/setfit_baai_newrelic_gpt-4o_cot-few_shot-instructions_only_reasoning_1726750400.408156")
166
+ # Run inference
167
+ preds = model("Evaluation:
168
+ The answer provided is concise and directly addresses the question of whom to contact for travel reimbursement questions. It correctly refers to the email address provided in the document. The answer is well-supported by the document and does not deviate into unrelated topics.
169
+
170
+ The final evaluation: Good")
171
+ ```
172
+
173
+ <!--
174
+ ### Downstream Use
175
+
176
+ *List how someone could finetune this model on their own dataset.*
177
+ -->
178
+
179
+ <!--
180
+ ### Out-of-Scope Use
181
+
182
+ *List how the model may foreseeably be misused and address what users ought not to do with the model.*
183
+ -->
184
+
185
+ <!--
186
+ ## Bias, Risks and Limitations
187
+
188
+ *What are the known or foreseeable issues stemming from this model? You could also flag here known failure cases or weaknesses of the model.*
189
+ -->
190
+
191
+ <!--
192
+ ### Recommendations
193
+
194
+ *What are recommendations with respect to the foreseeable issues? For example, filtering explicit content.*
195
+ -->
196
+
197
+ ## Training Details
198
+
199
+ ### Training Set Metrics
200
+ | Training set | Min | Median | Max |
201
+ |:-------------|:----|:---------|:----|
202
+ | Word count | 30 | 106.3538 | 221 |
203
+
204
+ | Label | Training Sample Count |
205
+ |:------|:----------------------|
206
+ | 0 | 32 |
207
+ | 1 | 33 |
208
+
209
+ ### Training Hyperparameters
210
+ - batch_size: (16, 16)
211
+ - num_epochs: (5, 5)
212
+ - max_steps: -1
213
+ - sampling_strategy: oversampling
214
+ - num_iterations: 20
215
+ - body_learning_rate: (2e-05, 2e-05)
216
+ - head_learning_rate: 2e-05
217
+ - loss: CosineSimilarityLoss
218
+ - distance_metric: cosine_distance
219
+ - margin: 0.25
220
+ - end_to_end: False
221
+ - use_amp: False
222
+ - warmup_proportion: 0.1
223
+ - l2_weight: 0.01
224
+ - seed: 42
225
+ - eval_max_steps: -1
226
+ - load_best_model_at_end: False
227
+
228
+ ### Training Results
229
+ | Epoch | Step | Training Loss | Validation Loss |
230
+ |:------:|:----:|:-------------:|:---------------:|
231
+ | 0.0061 | 1 | 0.2332 | - |
232
+ | 0.3067 | 50 | 0.2674 | - |
233
+ | 0.6135 | 100 | 0.2116 | - |
234
+ | 0.9202 | 150 | 0.0354 | - |
235
+ | 1.2270 | 200 | 0.0036 | - |
236
+ | 1.5337 | 250 | 0.0022 | - |
237
+ | 1.8405 | 300 | 0.0017 | - |
238
+ | 2.1472 | 350 | 0.0016 | - |
239
+ | 2.4540 | 400 | 0.0015 | - |
240
+ | 2.7607 | 450 | 0.0013 | - |
241
+ | 3.0675 | 500 | 0.0013 | - |
242
+ | 3.3742 | 550 | 0.0012 | - |
243
+ | 3.6810 | 600 | 0.0012 | - |
244
+ | 3.9877 | 650 | 0.0011 | - |
245
+ | 4.2945 | 700 | 0.0012 | - |
246
+ | 4.6012 | 750 | 0.0011 | - |
247
+ | 4.9080 | 800 | 0.0011 | - |
248
+
249
+ ### Framework Versions
250
+ - Python: 3.10.14
251
+ - SetFit: 1.1.0
252
+ - Sentence Transformers: 3.1.0
253
+ - Transformers: 4.44.0
254
+ - PyTorch: 2.4.1+cu121
255
+ - Datasets: 2.19.2
256
+ - Tokenizers: 0.19.1
257
+
258
+ ## Citation
259
+
260
+ ### BibTeX
261
+ ```bibtex
262
+ @article{https://doi.org/10.48550/arxiv.2209.11055,
263
+ doi = {10.48550/ARXIV.2209.11055},
264
+ url = {https://arxiv.org/abs/2209.11055},
265
+ author = {Tunstall, Lewis and Reimers, Nils and Jo, Unso Eun Seo and Bates, Luke and Korat, Daniel and Wasserblat, Moshe and Pereg, Oren},
266
+ keywords = {Computation and Language (cs.CL), FOS: Computer and information sciences, FOS: Computer and information sciences},
267
+ title = {Efficient Few-Shot Learning Without Prompts},
268
+ publisher = {arXiv},
269
+ year = {2022},
270
+ copyright = {Creative Commons Attribution 4.0 International}
271
+ }
272
+ ```
273
+
274
+ <!--
275
+ ## Glossary
276
+
277
+ *Clearly define terms in order to be accessible across audiences.*
278
+ -->
279
+
280
+ <!--
281
+ ## Model Card Authors
282
+
283
+ *Lists the people who create the model card, providing recognition and accountability for the detailed work that goes into its construction.*
284
+ -->
285
+
286
+ <!--
287
+ ## Model Card Contact
288
+
289
+ *Provides a way for people who have updates to the Model Card, suggestions, or questions, to contact the Model Card authors.*
290
+ -->
config.json ADDED
@@ -0,0 +1,32 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "_name_or_path": "BAAI/bge-base-en-v1.5",
3
+ "architectures": [
4
+ "BertModel"
5
+ ],
6
+ "attention_probs_dropout_prob": 0.1,
7
+ "classifier_dropout": null,
8
+ "gradient_checkpointing": false,
9
+ "hidden_act": "gelu",
10
+ "hidden_dropout_prob": 0.1,
11
+ "hidden_size": 768,
12
+ "id2label": {
13
+ "0": "LABEL_0"
14
+ },
15
+ "initializer_range": 0.02,
16
+ "intermediate_size": 3072,
17
+ "label2id": {
18
+ "LABEL_0": 0
19
+ },
20
+ "layer_norm_eps": 1e-12,
21
+ "max_position_embeddings": 512,
22
+ "model_type": "bert",
23
+ "num_attention_heads": 12,
24
+ "num_hidden_layers": 12,
25
+ "pad_token_id": 0,
26
+ "position_embedding_type": "absolute",
27
+ "torch_dtype": "float32",
28
+ "transformers_version": "4.44.0",
29
+ "type_vocab_size": 2,
30
+ "use_cache": true,
31
+ "vocab_size": 30522
32
+ }
config_sentence_transformers.json ADDED
@@ -0,0 +1,10 @@
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "__version__": {
3
+ "sentence_transformers": "3.1.0",
4
+ "transformers": "4.44.0",
5
+ "pytorch": "2.4.1+cu121"
6
+ },
7
+ "prompts": {},
8
+ "default_prompt_name": null,
9
+ "similarity_fn_name": null
10
+ }
config_setfit.json ADDED
@@ -0,0 +1,4 @@
 
 
 
 
 
1
+ {
2
+ "normalize_embeddings": false,
3
+ "labels": null
4
+ }
model.safetensors ADDED
@@ -0,0 +1,3 @@
 
 
 
 
1
+ version https://git-lfs.github.com/spec/v1
2
+ oid sha256:6bcb063f17262bad0004e0f65e27e3b8e1a78f692d14323520500efc13cdc329
3
+ size 437951328
model_head.pkl ADDED
@@ -0,0 +1,3 @@
 
 
 
 
1
+ version https://git-lfs.github.com/spec/v1
2
+ oid sha256:c6e15f1c9007ad31aa3e1b326654090fda1b2bb461006f5640d24ed4d0eb39eb
3
+ size 7007
modules.json ADDED
@@ -0,0 +1,20 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ [
2
+ {
3
+ "idx": 0,
4
+ "name": "0",
5
+ "path": "",
6
+ "type": "sentence_transformers.models.Transformer"
7
+ },
8
+ {
9
+ "idx": 1,
10
+ "name": "1",
11
+ "path": "1_Pooling",
12
+ "type": "sentence_transformers.models.Pooling"
13
+ },
14
+ {
15
+ "idx": 2,
16
+ "name": "2",
17
+ "path": "2_Normalize",
18
+ "type": "sentence_transformers.models.Normalize"
19
+ }
20
+ ]
sentence_bert_config.json ADDED
@@ -0,0 +1,4 @@
 
 
 
 
 
1
+ {
2
+ "max_seq_length": 512,
3
+ "do_lower_case": true
4
+ }
special_tokens_map.json ADDED
@@ -0,0 +1,37 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "cls_token": {
3
+ "content": "[CLS]",
4
+ "lstrip": false,
5
+ "normalized": false,
6
+ "rstrip": false,
7
+ "single_word": false
8
+ },
9
+ "mask_token": {
10
+ "content": "[MASK]",
11
+ "lstrip": false,
12
+ "normalized": false,
13
+ "rstrip": false,
14
+ "single_word": false
15
+ },
16
+ "pad_token": {
17
+ "content": "[PAD]",
18
+ "lstrip": false,
19
+ "normalized": false,
20
+ "rstrip": false,
21
+ "single_word": false
22
+ },
23
+ "sep_token": {
24
+ "content": "[SEP]",
25
+ "lstrip": false,
26
+ "normalized": false,
27
+ "rstrip": false,
28
+ "single_word": false
29
+ },
30
+ "unk_token": {
31
+ "content": "[UNK]",
32
+ "lstrip": false,
33
+ "normalized": false,
34
+ "rstrip": false,
35
+ "single_word": false
36
+ }
37
+ }
tokenizer.json ADDED
The diff for this file is too large to render. See raw diff
 
tokenizer_config.json ADDED
@@ -0,0 +1,57 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "added_tokens_decoder": {
3
+ "0": {
4
+ "content": "[PAD]",
5
+ "lstrip": false,
6
+ "normalized": false,
7
+ "rstrip": false,
8
+ "single_word": false,
9
+ "special": true
10
+ },
11
+ "100": {
12
+ "content": "[UNK]",
13
+ "lstrip": false,
14
+ "normalized": false,
15
+ "rstrip": false,
16
+ "single_word": false,
17
+ "special": true
18
+ },
19
+ "101": {
20
+ "content": "[CLS]",
21
+ "lstrip": false,
22
+ "normalized": false,
23
+ "rstrip": false,
24
+ "single_word": false,
25
+ "special": true
26
+ },
27
+ "102": {
28
+ "content": "[SEP]",
29
+ "lstrip": false,
30
+ "normalized": false,
31
+ "rstrip": false,
32
+ "single_word": false,
33
+ "special": true
34
+ },
35
+ "103": {
36
+ "content": "[MASK]",
37
+ "lstrip": false,
38
+ "normalized": false,
39
+ "rstrip": false,
40
+ "single_word": false,
41
+ "special": true
42
+ }
43
+ },
44
+ "clean_up_tokenization_spaces": true,
45
+ "cls_token": "[CLS]",
46
+ "do_basic_tokenize": true,
47
+ "do_lower_case": true,
48
+ "mask_token": "[MASK]",
49
+ "model_max_length": 512,
50
+ "never_split": null,
51
+ "pad_token": "[PAD]",
52
+ "sep_token": "[SEP]",
53
+ "strip_accents": null,
54
+ "tokenize_chinese_chars": true,
55
+ "tokenizer_class": "BertTokenizer",
56
+ "unk_token": "[UNK]"
57
+ }
vocab.txt ADDED
The diff for this file is too large to render. See raw diff