Netta1994 commited on
Commit
6fb041f
1 Parent(s): a7d0624

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,340 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
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: 'Reasoning why the answer may be good:
14
+
15
+ 1. **Context Grounding:** The answer correctly interprets and references the specific
16
+ part of the provided document that mentions the response status column.
17
+
18
+ 2. **Relevance:** The answer directly addresses the question by explaining what
19
+ the percentage in the response status column indicates.
20
+
21
+ 3. **Conciseness:** The answer is concise and avoids unnecessary information,
22
+ focusing solely on the meaning of the percentage in the response status column.
23
+
24
+ 4. **Specificity:** The answer gives a detailed explanation about what the percentage
25
+ represents—successful completion of response actions.
26
+
27
+ 5. **Accuracy:** The key concept of the percentage indicating the total amount
28
+ of successful completion of response actions is correctly conveyed as per the
29
+ document.
30
+
31
+
32
+ Reasoning why the answer may be bad:
33
+
34
+ There is no apparent reason for the answer to be bad; it aligns well with the
35
+ document and addresses the question directly and concisely.
36
+
37
+
38
+ Final result: Good'
39
+ - text: 'Reasoning:
40
+
41
+ **Why the answer may be good:**
42
+
43
+ - It accurately states that the provided information does not address the specific
44
+ question.
45
+
46
+ - It directs the reader to seek additional information or context.
47
+
48
+
49
+ **Why the answer may be bad:**
50
+
51
+ - It does not attempt to relate or infer an answer based on the document provided.
52
+
53
+ - The document does provide relevant details about endpoint controls, including
54
+ that they involve Device Control, Personal Firewall Control, and Full Disk Encryption
55
+ Visibility, which can imply their purpose.
56
+
57
+ - The response is somewhat evasive and does not leverage any context offered by
58
+ the document to give an informed answer.
59
+
60
+
61
+ Final Result: Bad'
62
+ - text: 'Reasoning why the answer may be good:
63
+
64
+ - The provided answer is addressing the purpose of an agent (collecting and securely
65
+ forwarding logs), aligning with the context of log collection and forwarding described
66
+ in the document.
67
+
68
+
69
+ Reasoning why the answer may be bad:
70
+
71
+ - The answer is missing specificity. It does not mention on-site collection nor
72
+ does it specify the direct forwarding feature mentioned in the document.
73
+
74
+ - It lacks details specified in the document about the agent being used for integrations
75
+ that do not use cloud feeds, e.g., firewalls.
76
+
77
+ - The answer does not mention <ORGANIZATION> explicitly ties into the detection
78
+ and correlation engine.
79
+
80
+
81
+ Final result: Bad'
82
+ - text: '### Reasoning
83
+
84
+
85
+ **Good Aspects of the Answer:**
86
+
87
+ 1. **Context Grounding:** The answer correctly pulls context from the document
88
+ regarding email notifications.
89
+
90
+ 2. **Relevance:** The answer attempts to address the purpose of the email notifications
91
+ checkbox directly.
92
+
93
+
94
+ **Bad Aspects of the Answer:**
95
+
96
+ 1. **Key/Value/Event Name Accuracy:** The document outlines a checkbox related
97
+ to enabling or disabling email notifications, but the answer uses placeholder
98
+ text "ORGANIZATION_2," which needs replacement for accuracy.
99
+
100
+ 2. **Conciseness:** The answer is somewhat repetitive with the phrasing "ORGANIZATION_2
101
+ or disable," which should clearly state "enable or disable."
102
+
103
+ 3. **Specificity:** The answer lacks the specific detail from the document that
104
+ this is specific to stale or archived sensors and involves System Admins.
105
+
106
+
107
+ ### Final Evaluation
108
+
109
+
110
+ **Final Result:** `Bad`
111
+
112
+
113
+ The placeholder text makes the information ambiguous and not actionable. Additionally,
114
+ there is a slight redundancy and missing specific roles (System Admin) and context
115
+ (stale/archived sensors) necessary for precision.'
116
+ - text: 'Reasoning why the answer may be good:
117
+
118
+ - The answer provides a specific URL, which is required by the question.
119
+
120
+ - It appears to be in the format expected for image URLs as hinted at in the document.
121
+
122
+
123
+ Reasoning why the answer may be bad:
124
+
125
+ - The provided answer does not match the precise URL given in the document.
126
+
127
+ - The correct URL for the second query should be `..\/..\/_images\/hunting_http://miller.co`,
128
+ while the answer contains `hunting_http://www.flores.net/`, which is not mentioned
129
+ in the document.
130
+
131
+ - The answer does not reflect careful cross-referencing with the provided document.
132
+
133
+
134
+ Final result: Bad'
135
+ inference: true
136
+ model-index:
137
+ - name: SetFit with BAAI/bge-base-en-v1.5
138
+ results:
139
+ - task:
140
+ type: text-classification
141
+ name: Text Classification
142
+ dataset:
143
+ name: Unknown
144
+ type: unknown
145
+ split: test
146
+ metrics:
147
+ - type: accuracy
148
+ value: 0.4788732394366197
149
+ name: Accuracy
150
+ ---
151
+
152
+ # SetFit with BAAI/bge-base-en-v1.5
153
+
154
+ 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.
155
+
156
+ The model has been trained using an efficient few-shot learning technique that involves:
157
+
158
+ 1. Fine-tuning a [Sentence Transformer](https://www.sbert.net) with contrastive learning.
159
+ 2. Training a classification head with features from the fine-tuned Sentence Transformer.
160
+
161
+ ## Model Details
162
+
163
+ ### Model Description
164
+ - **Model Type:** SetFit
165
+ - **Sentence Transformer body:** [BAAI/bge-base-en-v1.5](https://huggingface.co/BAAI/bge-base-en-v1.5)
166
+ - **Classification head:** a [LogisticRegression](https://scikit-learn.org/stable/modules/generated/sklearn.linear_model.LogisticRegression.html) instance
167
+ - **Maximum Sequence Length:** 512 tokens
168
+ - **Number of Classes:** 2 classes
169
+ <!-- - **Training Dataset:** [Unknown](https://huggingface.co/datasets/unknown) -->
170
+ <!-- - **Language:** Unknown -->
171
+ <!-- - **License:** Unknown -->
172
+
173
+ ### Model Sources
174
+
175
+ - **Repository:** [SetFit on GitHub](https://github.com/huggingface/setfit)
176
+ - **Paper:** [Efficient Few-Shot Learning Without Prompts](https://arxiv.org/abs/2209.11055)
177
+ - **Blogpost:** [SetFit: Efficient Few-Shot Learning Without Prompts](https://huggingface.co/blog/setfit)
178
+
179
+ ### Model Labels
180
+ | Label | Examples |
181
+ |:------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
182
+ | 0 | <ul><li>'Reasoning why the answer may be good:\n- The answer attempts to address the significance of considering all the answers together, which is the core of the question.\n\nReasoning why the answer may be bad:\n- The provided answer does not specifically mention or directly link to the key points raised in the provided document.\n- It lacks specificity and grounding in the text, failing to reference important considerations such as the significance of the machines involved, the severity of the behavior, and the significance of the users involved.\n- It does not directly explain why combining all the answers aids in determining if the behavior is malicious.\n\nFinal Result: Bad'</li><li>'The answer provided is:\n\n"The information provided doesn\'t cover this specific query. Please refer to additional sources or provide more context to obtain a comprehensive answer."\n\n### Evaluation\n\n**1. Context Grounding:** \n- **Negative:** The provided document actually contains a detailed procedure for excluding MalOps. The answer incorrectly claims the information does not cover the query.\n\n**2. Relevance:** \n- **Negative:** The answer does not address the question of what the process is, instead, it diverts the user to additional sources.\n\n**3. Conciseness:** \n- **Negative:** It doesn\'t provide concise information pertinent to the question asked.\n\n**4. Specificity:** \n- **Negative:** The answer is too general and lacks any specifics related to the step-by-step process detailed in the document.\n\n**5. Correct Key/Value/Event Name:**\n- **Negative:** No keys or values related to the exclusion process (like “Exclude” or “allowlist”) are mentioned, which the document clearly outlines.\n\n### Reasoning\n\n- **Good points:** There are actually no good points since the answer is incorrect and not useful.\n- **Bad points:** The answer dismisses the information when the procedure is clearly mapped out in the document. It fails to provide the necessary details from the document.\n\n### Final Result\n**Bad**'</li><li>'**Reasoning:**\n\n**Good Elements:**\n1. **Conciseness:** The provided answer is concise and directly specifies the action needed for a quarantined file.\n2. **Relevance:** The answer directly addresses the question, mentioning that the file should be un-quarantined.\n\n**Bad Elements:**\n1. **Context Grounding:** The answer only partially references the document without showing a comprehensive understanding.\n2. **Completeness:** The answer mentions un-quarantining but does not provide specifics about the subsequent steps needed for submitting a quarantined file as a false positive.\n3. **Format and Clarity:** It omits the mention of the prerequisite or steps for un-quarantining mentioned in the document.\n\n**Final Result:**\n**Bad** \nThe answer is accurate but lacks the necessary depth and context to be fully correct. It should have included the pre-requisite and clarified the steps for submission after un-quarantining.'</li></ul> |
183
+ | 1 | <ul><li>'**Reasoning:**\n\n**Positive Aspects:**\n1. **Context Grounding:** The answer mentions a dump file and relates it to the contents of the sensor’s RAM at the time of failure, which is consistent with the provided document.\n2. **Relevance:** The answer is directed at what the computer generates in case of a system failure.\n\n**Negative Aspects:**\n1. **Specificity:** While it correctly mentions that the dump file contains the entire contents of the sensor\'s RAM at the time of the failure, it does not clearly state specifically that it is a "memory dump file," which would be more precise.\n2. **Terminology:** The document uses the term "memory dump file," which is more accurate and would align better with the terminology used in the question and document.\n3. **Conciseness:** It could be perceived as slightly verbose given the requirement for direct and precise information.\n\nGiven these points, the answer could be clearer and more specific in the terminology used.\n\n**Final Result:** **Bad**'</li><li>'**Evaluation Reasoning:**\n\n1. **Context Grounding:**\n - **Good Aspect:** The answer is derived from the document where it mentions threat detection as a core capability of the <ORGANIZATION_2> platforms to identify cyber security threats.\n - **Bad Aspect:** The answer is vague and doesn’t leverage the detailed explanation provided in the document, which talks about using advanced engines, AI, ML, and behavioral analysis to identify cyber security threats.\n\n2. **Relevance:**\n - **Good Aspect:** The answer addresses the specific question about the purpose of the <ORGANIZATION_2> platforms threat detection abilities.\n - **Bad Aspect:** It fails to incorporate how the document details the processes (use of AI, ML, etc.) to identify threats.\n\n3. **Conciseness:**\n - **Good Aspect:** The answer is definitely concise.\n - **Bad Aspect:** It is overly concise to the point of lacking necessary detail, which makes it too general and uninformative.\n\n4. **Specificity:**\n - **Good Aspect:** The basic idea of identifying cyber security threats is correct.\n - **Bad Aspect:** It omits specific key elements such as AI, machine learning, and behavioral analysis mentioned in the document.\n\n5. **Accuracy regarding key/value/event name:** \n - **Good Aspect:** "Identifying cyber security threats" is a correct general purpose.\n - **Bad Aspect:** The answer does not mention specifically the details related to the ENGINE or specific methods/tools involved, nor does it leverage the details of how the platform operates.\n\n**Final Evaluation Result:**\nBad'</li><li>'Reasoning:\n\n**Good Points**:\n- The answer directly addresses the lack of coverage in the provided document regarding the specific query.\n\n**Bad Points**:\n- The answer is incorrect because it states there is no information on the fifth scenario, but the document provides examples, and the evaluator should infer which of the mentioned scenarios could be considered the fifth if it was in sequence.\n- The answer does not leverage any context from the document, failing at providing even an approximate related response.\n- The answer lacks specificity and does not attempt to relate to any scenarios described.\n\nFinal Result: Bad'</li></ul> |
184
+
185
+ ## Evaluation
186
+
187
+ ### Metrics
188
+ | Label | Accuracy |
189
+ |:--------|:---------|
190
+ | **all** | 0.4789 |
191
+
192
+ ## Uses
193
+
194
+ ### Direct Use for Inference
195
+
196
+ First install the SetFit library:
197
+
198
+ ```bash
199
+ pip install setfit
200
+ ```
201
+
202
+ Then you can load this model and run inference.
203
+
204
+ ```python
205
+ from setfit import SetFitModel
206
+
207
+ # Download from the 🤗 Hub
208
+ model = SetFitModel.from_pretrained("Netta1994/setfit_baai_cybereason_gpt-4o_improved-cot-instructions_two_reasoning_only_reasoning_")
209
+ # Run inference
210
+ preds = model("Reasoning why the answer may be good:
211
+ - The answer provides a specific URL, which is required by the question.
212
+ - It appears to be in the format expected for image URLs as hinted at in the document.
213
+
214
+ Reasoning why the answer may be bad:
215
+ - The provided answer does not match the precise URL given in the document.
216
+ - The correct URL for the second query should be `..\/..\/_images\/hunting_http://miller.co`, while the answer contains `hunting_http://www.flores.net/`, which is not mentioned in the document.
217
+ - The answer does not reflect careful cross-referencing with the provided document.
218
+
219
+ Final result: Bad")
220
+ ```
221
+
222
+ <!--
223
+ ### Downstream Use
224
+
225
+ *List how someone could finetune this model on their own dataset.*
226
+ -->
227
+
228
+ <!--
229
+ ### Out-of-Scope Use
230
+
231
+ *List how the model may foreseeably be misused and address what users ought not to do with the model.*
232
+ -->
233
+
234
+ <!--
235
+ ## Bias, Risks and Limitations
236
+
237
+ *What are the known or foreseeable issues stemming from this model? You could also flag here known failure cases or weaknesses of the model.*
238
+ -->
239
+
240
+ <!--
241
+ ### Recommendations
242
+
243
+ *What are recommendations with respect to the foreseeable issues? For example, filtering explicit content.*
244
+ -->
245
+
246
+ ## Training Details
247
+
248
+ ### Training Set Metrics
249
+ | Training set | Min | Median | Max |
250
+ |:-------------|:----|:---------|:----|
251
+ | Word count | 60 | 128.2029 | 239 |
252
+
253
+ | Label | Training Sample Count |
254
+ |:------|:----------------------|
255
+ | 0 | 34 |
256
+ | 1 | 35 |
257
+
258
+ ### Training Hyperparameters
259
+ - batch_size: (16, 16)
260
+ - num_epochs: (5, 5)
261
+ - max_steps: -1
262
+ - sampling_strategy: oversampling
263
+ - num_iterations: 20
264
+ - body_learning_rate: (2e-05, 2e-05)
265
+ - head_learning_rate: 2e-05
266
+ - loss: CosineSimilarityLoss
267
+ - distance_metric: cosine_distance
268
+ - margin: 0.25
269
+ - end_to_end: False
270
+ - use_amp: False
271
+ - warmup_proportion: 0.1
272
+ - l2_weight: 0.01
273
+ - seed: 42
274
+ - eval_max_steps: -1
275
+ - load_best_model_at_end: False
276
+
277
+ ### Training Results
278
+ | Epoch | Step | Training Loss | Validation Loss |
279
+ |:------:|:----:|:-------------:|:---------------:|
280
+ | 0.0058 | 1 | 0.2486 | - |
281
+ | 0.2890 | 50 | 0.2626 | - |
282
+ | 0.5780 | 100 | 0.2394 | - |
283
+ | 0.8671 | 150 | 0.1005 | - |
284
+ | 1.1561 | 200 | 0.0028 | - |
285
+ | 1.4451 | 250 | 0.002 | - |
286
+ | 1.7341 | 300 | 0.0018 | - |
287
+ | 2.0231 | 350 | 0.0016 | - |
288
+ | 2.3121 | 400 | 0.0016 | - |
289
+ | 2.6012 | 450 | 0.0014 | - |
290
+ | 2.8902 | 500 | 0.0013 | - |
291
+ | 3.1792 | 550 | 0.0012 | - |
292
+ | 3.4682 | 600 | 0.0012 | - |
293
+ | 3.7572 | 650 | 0.0012 | - |
294
+ | 4.0462 | 700 | 0.0012 | - |
295
+ | 4.3353 | 750 | 0.0012 | - |
296
+ | 4.6243 | 800 | 0.0011 | - |
297
+ | 4.9133 | 850 | 0.0011 | - |
298
+
299
+ ### Framework Versions
300
+ - Python: 3.10.14
301
+ - SetFit: 1.1.0
302
+ - Sentence Transformers: 3.1.0
303
+ - Transformers: 4.44.0
304
+ - PyTorch: 2.4.1+cu121
305
+ - Datasets: 2.19.2
306
+ - Tokenizers: 0.19.1
307
+
308
+ ## Citation
309
+
310
+ ### BibTeX
311
+ ```bibtex
312
+ @article{https://doi.org/10.48550/arxiv.2209.11055,
313
+ doi = {10.48550/ARXIV.2209.11055},
314
+ url = {https://arxiv.org/abs/2209.11055},
315
+ author = {Tunstall, Lewis and Reimers, Nils and Jo, Unso Eun Seo and Bates, Luke and Korat, Daniel and Wasserblat, Moshe and Pereg, Oren},
316
+ keywords = {Computation and Language (cs.CL), FOS: Computer and information sciences, FOS: Computer and information sciences},
317
+ title = {Efficient Few-Shot Learning Without Prompts},
318
+ publisher = {arXiv},
319
+ year = {2022},
320
+ copyright = {Creative Commons Attribution 4.0 International}
321
+ }
322
+ ```
323
+
324
+ <!--
325
+ ## Glossary
326
+
327
+ *Clearly define terms in order to be accessible across audiences.*
328
+ -->
329
+
330
+ <!--
331
+ ## Model Card Authors
332
+
333
+ *Lists the people who create the model card, providing recognition and accountability for the detailed work that goes into its construction.*
334
+ -->
335
+
336
+ <!--
337
+ ## Model Card Contact
338
+
339
+ *Provides a way for people who have updates to the Model Card, suggestions, or questions, to contact the Model Card authors.*
340
+ -->
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
+ "labels": null,
3
+ "normalize_embeddings": false
4
+ }
model.safetensors ADDED
@@ -0,0 +1,3 @@
 
 
 
 
1
+ version https://git-lfs.github.com/spec/v1
2
+ oid sha256:d2503f996087bab716ce7c88aae541793a5a791f24c571571ac0817dbd2e0f49
3
+ size 437951328
model_head.pkl ADDED
@@ -0,0 +1,3 @@
 
 
 
 
1
+ version https://git-lfs.github.com/spec/v1
2
+ oid sha256:25145958464876fdd251af2ab8a0e4c88869cb7ebcb127fafd030add81bc2cb4
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