ChenyuEcho commited on
Commit
0b6c7df
·
verified ·
1 Parent(s): 6c2448c

Upload folder using huggingface_hub

Browse files
.gitattributes CHANGED
@@ -33,3 +33,4 @@ saved_model/**/* filter=lfs diff=lfs merge=lfs -text
33
  *.zip filter=lfs diff=lfs merge=lfs -text
34
  *.zst filter=lfs diff=lfs merge=lfs -text
35
  *tfevents* filter=lfs diff=lfs merge=lfs -text
 
 
33
  *.zip filter=lfs diff=lfs merge=lfs -text
34
  *.zst filter=lfs diff=lfs merge=lfs -text
35
  *tfevents* filter=lfs diff=lfs merge=lfs -text
36
+ tokenizer.json filter=lfs diff=lfs merge=lfs -text
1_Pooling/config.json ADDED
@@ -0,0 +1,10 @@
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "word_embedding_dimension": 1024,
3
+ "pooling_mode_cls_token": false,
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": true,
9
+ "include_prompt": true
10
+ }
README.md ADDED
@@ -0,0 +1,847 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ ---
2
+ tags:
3
+ - sentence-transformers
4
+ - sentence-similarity
5
+ - feature-extraction
6
+ - dense
7
+ - generated_from_trainer
8
+ - dataset_size:2394
9
+ - loss:MultipleNegativesRankingLoss
10
+ base_model: Qwen/Qwen3-Embedding-0.6B
11
+ widget:
12
+ - source_sentence: 'Hendricks case: confidential incident details discussed with OR
13
+ staff outside the formal investigation process'
14
+ sentences:
15
+ - 'Subject: Concerns Regarding Recent Dietary Services Menu Change
16
+
17
+ From: Laura A. Hughes
18
+
19
+ To: Elizabeth M. Turner
20
+
21
+ Date: 2026-01-16
22
+
23
+
24
+ Hello Elizabeth,
25
+
26
+
27
+ I am reaching out to bring to your attention several patient concerns that have
28
+ arisen following the recent dietary services menu change implemented last week.
29
+ Multiple patients and their families have noted a lack of clarity regarding allergen
30
+ labeling and have expressed confusion about the new meal selections. In light
31
+ of our patient safety protocols, I recommend we conduct a rapid review of current
32
+ menu documentation and consider a focused staff in-service to address labeling
33
+ accuracy and communication with patients. Please let me know if you require detailed
34
+ feedback reports or would like to coordinate a joint review meeting to address
35
+ these issues collectively.
36
+
37
+
38
+ Best regards,
39
+
40
+ Laura A. Hughes'
41
+ - 'Subject: Patient Safety Week Activities: Join Us in Fostering a Culture of Safety
42
+
43
+ From: Diane L. Cooper
44
+
45
+ To: All Hospital Staff
46
+
47
+ Date: 2025-10-12
48
+
49
+
50
+ Dear St. Catherine''s Team,
51
+
52
+
53
+ As we approach National Patient Safety Week, I am pleased to invite all staff
54
+ to participate in a series of activities dedicated to reinforcing our shared commitment
55
+ to patient safety and quality care. Throughout the week, we will host educational
56
+ workshops, interactive safety simulations, and informative sessions led by our
57
+ hospital''s clinical risk management team. These events are designed not only
58
+ to enhance our understanding of best practices but also to empower every one of
59
+ us in proactively promoting a safe hospital environment.
60
+
61
+
62
+ Patient safety remains at the heart of our mission, and your engagement is instrumental
63
+ in upholding our standards. I encourage everyone to review the attached schedule
64
+ and make time to participate in as many sessions as possible. Together, let’s
65
+ continue to cultivate transparency, learning, and collaboration across all departments.
66
+
67
+
68
+ Should you have any questions regarding the activities or wish to suggest additional
69
+ topics, please do not hesitate to reach out to me directly.
70
+
71
+
72
+ Thank you for your dedication to excellence and patient care.
73
+
74
+
75
+ Best regards,
76
+
77
+ Diane L. Cooper
78
+
79
+ Director, Employee Relations
80
+
81
+ St. Catherine''s Regional Hospital'
82
+ - 'Subject: Required Meeting: Performance and Policy Compliance
83
+
84
+ From: Patricia M. Vasquez
85
+
86
+ To: Sarah J. Morrison
87
+
88
+ Date: 2025-09-17
89
+
90
+
91
+ Dear Sarah,
92
+
93
+
94
+ Thank you for your prompt reply and for confirming your attendance at the meeting.
95
+ To address your request for clarification, we have received reports that you have
96
+ been discussing confidential incident details related to the Hendricks case with
97
+ OR staff members outside the formal investigation process. Additionally, it has
98
+ been noted that your characterization of events in those discussions has been
99
+ inconsistent with your formal statements submitted to patient safety and risk
100
+ management.
101
+
102
+
103
+ Given the seriousness of these concerns, we will discuss them in detail during
104
+ our meeting on Thursday. I urge you to consider carefully how you want to proceed
105
+ with your employment here and to review any relevant documentation in advance.
106
+ If you have further questions, please let me know.
107
+
108
+
109
+ Regards,
110
+
111
+ Patricia M. Vasquez
112
+
113
+ Risk Management Director'
114
+ - source_sentence: Who is responsible for coordinating with Employee Health to establish
115
+ overnight or mobile flu vaccination slots for Radiology and Ultrasound night-shift
116
+ staff, and what is the timeline to implement it?
117
+ sentences:
118
+ - 'Subject: Issue with Patient Portal Enrollment Impacting Billing Documentation
119
+
120
+ From: Sofia R. Ramirez
121
+
122
+ To: George M. Harris
123
+
124
+ Date: 2025-11-11
125
+
126
+
127
+ Hi George,
128
+
129
+
130
+ I''m reaching out because I''ve noticed several cases where new patients are unable
131
+ to complete their portal enrollment, which has led to incomplete demographic and
132
+ insurance information in our records. This is causing issues with proper billing
133
+ code assignment and delays in claims processing. Do you have recommendations for
134
+ improving the collection of required documentation at this stage or a workflow
135
+ update that could help ensure all necessary data is captured before billing? Your
136
+ expertise would be invaluable as we try to minimize claim denials due to missing
137
+ information.
138
+
139
+
140
+ Thanks for your help,
141
+
142
+ Sofia'
143
+ - 'Subject: Concern Regarding Central Line Infection Rate and Equipment Protocols
144
+
145
+ From: Daniel M. Evans
146
+
147
+ To: Thomas R. Anderson
148
+
149
+ Date: 2025-09-29
150
+
151
+
152
+ Hi Thomas,
153
+
154
+
155
+ I wanted to bring to your attention a recent uptick in the central line infection
156
+ rates reported on Med-Surg units over the past two weeks. My initial review suggests
157
+ possible inconsistencies in how central line carts are being sanitized and restocked
158
+ during overnight shifts, especially with high patient turnover. I recommend we
159
+ conduct a targeted refresher with night staff and consider updating signage on
160
+ carts to reinforce proper protocol. Could you assist in coordinating this or suggest
161
+ an alternate approach to address the issue promptly?
162
+
163
+
164
+ Thanks for your leadership,
165
+
166
+ Daniel
167
+
168
+
169
+ Get Outlook for iOS'
170
+ - 'Subject: Flu Vaccination Campaign: Night Shift Coverage Concern
171
+
172
+ From: Jasmine K. Patel
173
+
174
+ To: Thomas R. Anderson
175
+
176
+ Date: 2026-01-19
177
+
178
+
179
+ Hi Thomas,
180
+
181
+
182
+ I wanted to flag an issue regarding the ongoing flu vaccination campaign. We''ve
183
+ noticed that several night shift staff in Radiology and Ultrasound have missed
184
+ scheduled vaccine appointments due to limited after-hours availability. Would
185
+ it be possible to coordinate with Employee Health to set up a dedicated time slot
186
+ overnight or provide mobile vaccination rounds for these teams?
187
+
188
+
189
+ Let me know how you''d like to proceed.
190
+
191
+
192
+ Thanks,
193
+
194
+ Jasmine'
195
+ - source_sentence: Confirm availability of Room 214 or an alternative near the kitchen
196
+ for a dietary workshop scheduled 2-4 pm on the upcoming Thursday.
197
+ sentences:
198
+ - 'Subject: Incident Report: PACS System Downtime Impacting Surgical Workflow
199
+
200
+ From: Chloe R. Anderson
201
+
202
+ To: Ronald J. Mitchell
203
+
204
+ Date: 2025-12-17
205
+
206
+
207
+ Hi Ronald,
208
+
209
+
210
+ Thank you for your prompt response regarding the PACS system downtime in OR 3.
211
+ I appreciate your commitment to coordinating with IT and implementing interim
212
+ manual image access protocols, as well as initiating a root cause analysis. I
213
+ will continue to document any further disruptions, as requested, and look forward
214
+ to your update on both interim procedures and the proposed action plan within
215
+ the next 48 hours. Please let me know if there are any specific details or examples
216
+ you require for the analysis, as I am happy to provide additional documentation
217
+ or feedback to support the resolution process.
218
+
219
+
220
+ Best regards,
221
+
222
+ Chloe'
223
+ - 'Subject: Medication Inventory Shortage Affecting CT Protocols
224
+
225
+ From: Maya S. Patel
226
+
227
+ To: Emily T. O''Brien
228
+
229
+ Date: 2025-12-19
230
+
231
+
232
+ Hi Emily,
233
+
234
+
235
+ Thank you for bringing this urgent medication shortage to my attention. I appreciate
236
+ you taking the initiative to check with pharmacy first, and I completely understand
237
+ the impact limited Omnipaque has on critical CT procedures, particularly for stroke
238
+ and trauma protocols. I will immediately reach out to Materials Management to
239
+ find out the status of the incoming shipment and see if there are any options
240
+ for expediting delivery. Additionally, I’ll consult with Radiology and Pharmacy
241
+ leadership to review possible alternative contrast agents that could be safely
242
+ substituted without compromising patient care or compliance. I’ll provide you
243
+ with an update later today as soon as I have more information.
244
+
245
+
246
+ Please let me know if there are any specific cases you’re concerned about in the
247
+ interim so we can prioritize resources accordingly.
248
+
249
+
250
+ Thank you again for your vigilance on this issue.
251
+
252
+
253
+ Best regards,
254
+
255
+ Maya'
256
+ - 'Subject: Request for Room Reservation for Upcoming Dietary Workshop
257
+
258
+ From: Mary E. Carter
259
+
260
+ To: Barbara J. Young
261
+
262
+ Date: 2025-10-20
263
+
264
+
265
+ Hi Barbara,
266
+
267
+
268
+ I hope you’re doing well. I’d like to request a room reservation for our upcoming
269
+ dietary workshop scheduled next Thursday from 2-4 pm. We''ll be reviewing new
270
+ meal service procedures and want to cover updates on handling specific dietary
271
+ restrictions for patients. Ideally, we’ll need a space near the kitchen to facilitate
272
+ the hands-on demonstration segment. Could you please confirm if Room 214 or another
273
+ suitable room is available during that time? Timely confirmation would be greatly
274
+ appreciated so I can coordinate our kitchen staff and prepare the necessary materials.
275
+
276
+
277
+ Thank you for your help!
278
+
279
+
280
+ Best regards,
281
+
282
+ Mary'
283
+ - source_sentence: What are the exact policy violations alleged in relation to the
284
+ Hendricks incident referenced in the incident report?
285
+ sentences:
286
+ - 'Subject: Required Meeting: Performance and Policy Compliance
287
+
288
+ From: Sarah J. Morrison
289
+
290
+ To: Patricia M. Vasquez
291
+
292
+ Date: 2025-10-02
293
+
294
+
295
+ Dear Patricia,
296
+
297
+
298
+ Thank you for your message. I am quite concerned and honestly confused by the
299
+ allegations you referenced. I want to clarify that I have only discussed the Hendricks
300
+ incident with patient safety personnel and the individuals you specifically directed
301
+ me to meet with as part of the internal review process. At no point have I shared
302
+ confidential patient safety matters outside of these channels, and I have not
303
+ violated any HIPAA rules to my knowledge.
304
+
305
+
306
+ Could you please provide more details regarding the specific policy violations
307
+ being alleged? Is this related to my recent incident report concerning the Hendricks
308
+ case? I want to ensure I understand the nature of the concerns so I can respond
309
+ appropriately and prepare for our meeting. Please let me know what information
310
+ you need from me and when you would like to schedule this discussion.
311
+
312
+
313
+ I appreciate your clarification and look forward to resolving this matter.
314
+
315
+
316
+ Sincerely,
317
+
318
+ Sarah J. Morrison'
319
+ - 'Subject: Hinweis zu Systemfunktion – Bitte prüfen
320
+
321
+ From: Andrew J. Bennett
322
+
323
+ To: Angela R. Scott
324
+
325
+ Date: 2025-09-29
326
+
327
+
328
+ Hallo Angela,
329
+
330
+
331
+ ich wollte dich kurz auf ein mögliches Problem mit der Dokumentenarchivierungsfunktion
332
+ im neuen EHR-Update aufmerksam machen. Einige Nutzer haben Rückmeldungen gegeben,
333
+ dass freigegebene Laborbefunde nicht wie vorgesehen in den Patientenakten angezeigt
334
+ werden. Das könnte Auswirkungen auf die klinische Entscheidungsfindung haben.
335
+ Kannst du das bitte prüfen und mir eine Rückmeldung geben, ob wir mit einem Patch
336
+ rechnen können? Ich danke dir im Voraus für deine Unterstützung.
337
+
338
+
339
+ Viele Grüße,
340
+
341
+ Andrew'
342
+ - 'Subject: Defibrillator Battery Checks – Immediate Attention Required
343
+
344
+ From: Robert Kim
345
+
346
+ To: Jennifer Rodriguez
347
+
348
+ Date: 2025-12-03
349
+
350
+
351
+ Hi Jennifer,
352
+
353
+ I''ve noticed repeated inconsistencies with the battery checks on several OR defibrillators
354
+ over the past two weeks—twice now, devices have shown low battery during pre-op
355
+ review. This poses unnecessary risk and disrupts our workflow in critical cases.
356
+ I propose we assign a single OR tech to conduct and document battery checks at
357
+ the start of each shift, to ensure accountability and avoid gaps in readiness.
358
+ Please advise if you support this approach or can suggest a more robust solution.
359
+
360
+ Best,
361
+
362
+ Robert'
363
+ - source_sentence: What is the proposed date/time for a meeting with Maintenance to
364
+ review findings and strategize a remediation plan for OR wing HVAC fluctuations
365
+ affecting post-op mobility protocols?
366
+ sentences:
367
+ - 'Subject: Request for Conference Call Number
368
+
369
+ From: Carol A. Campbell
370
+
371
+ To: Melissa K. King
372
+
373
+ Date: 2025-10-27
374
+
375
+
376
+ Hi Melissa,
377
+
378
+
379
+ I hope you''re doing well. I am reaching out to request the conference call number
380
+ for our upcoming credentialing review meeting scheduled later this week. Having
381
+ the dial-in details ahead of time will help me circulate the information to all
382
+ committee members and ensure we are fully prepared to discuss the physician files
383
+ on the agenda. Please let me know at your earliest convenience if there are any
384
+ specific protocols or security codes required for access.
385
+
386
+
387
+ Thank you very much for your assistance.
388
+
389
+
390
+ Best regards,
391
+
392
+ Carol'
393
+ - 'Subject: Payment Posting Discrepancy – Assistance Needed with Discharge Billing
394
+
395
+ From: Isaiah T. Jackson
396
+
397
+ To: Taylor A. Richardson
398
+
399
+ Date: 2025-10-30
400
+
401
+
402
+ Hi Taylor,
403
+
404
+
405
+ Thanks for bringing this to my attention. I''ve pulled the discharge plan and
406
+ placement records and will cross-reference them with the insurance authorization
407
+ to verify alignment. Once I have more clarity, I’ll coordinate with you and finance
408
+ as needed to resolve any discrepancies—please hold off on correction for now.
409
+ If I require any additional documentation, I’ll let you know.
410
+
411
+
412
+ Best,
413
+
414
+ Isaiah'
415
+ - 'Subject: HVAC System Issues Impacting OR Wing: Request for Collaborative Solution
416
+
417
+ From: Dr. Susan L. Chang
418
+
419
+ To: Brian K. Lee
420
+
421
+ Date: 2025-10-20
422
+
423
+
424
+ Hi Brian,
425
+
426
+
427
+ Thank you for raising this concern regarding the HVAC fluctuations in the OR wing.
428
+ My team has indeed noticed some difficulties in maintaining prescribed post-operative
429
+ mobility protocols due to variable temperatures, which can discourage early patient
430
+ movement and affect our recovery benchmarks. I agree that partnering with Maintenance
431
+ for timely remediation is essential; I can share specific observations from our
432
+ unit that might help guide targeted improvements in the HVAC settings or scheduling.
433
+
434
+
435
+ Let me know when would be best to meet with you and Maintenance so we can review
436
+ findings and strategize a plan. Thanks again for the proactive outreach.
437
+
438
+
439
+ Best,
440
+
441
+ Susan'
442
+ pipeline_tag: sentence-similarity
443
+ library_name: sentence-transformers
444
+ metrics:
445
+ - cosine_accuracy@1
446
+ - cosine_accuracy@3
447
+ - cosine_accuracy@5
448
+ - cosine_accuracy@10
449
+ - cosine_precision@1
450
+ - cosine_precision@3
451
+ - cosine_precision@5
452
+ - cosine_precision@10
453
+ - cosine_recall@1
454
+ - cosine_recall@3
455
+ - cosine_recall@5
456
+ - cosine_recall@10
457
+ - cosine_ndcg@10
458
+ - cosine_mrr@10
459
+ - cosine_map@100
460
+ model-index:
461
+ - name: SentenceTransformer based on Qwen/Qwen3-Embedding-0.6B
462
+ results:
463
+ - task:
464
+ type: information-retrieval
465
+ name: Information Retrieval
466
+ dataset:
467
+ name: val evaluation
468
+ type: val_evaluation
469
+ metrics:
470
+ - type: cosine_accuracy@1
471
+ value: 0.8948247078464107
472
+ name: Cosine Accuracy@1
473
+ - type: cosine_accuracy@3
474
+ value: 0.9582637729549248
475
+ name: Cosine Accuracy@3
476
+ - type: cosine_accuracy@5
477
+ value: 0.9799666110183639
478
+ name: Cosine Accuracy@5
479
+ - type: cosine_accuracy@10
480
+ value: 1.0
481
+ name: Cosine Accuracy@10
482
+ - type: cosine_precision@1
483
+ value: 0.8948247078464107
484
+ name: Cosine Precision@1
485
+ - type: cosine_precision@3
486
+ value: 0.3194212576516416
487
+ name: Cosine Precision@3
488
+ - type: cosine_precision@5
489
+ value: 0.19599332220367274
490
+ name: Cosine Precision@5
491
+ - type: cosine_precision@10
492
+ value: 0.09999999999999999
493
+ name: Cosine Precision@10
494
+ - type: cosine_recall@1
495
+ value: 0.8948247078464107
496
+ name: Cosine Recall@1
497
+ - type: cosine_recall@3
498
+ value: 0.9582637729549248
499
+ name: Cosine Recall@3
500
+ - type: cosine_recall@5
501
+ value: 0.9799666110183639
502
+ name: Cosine Recall@5
503
+ - type: cosine_recall@10
504
+ value: 1.0
505
+ name: Cosine Recall@10
506
+ - type: cosine_ndcg@10
507
+ value: 0.947164718374032
508
+ name: Cosine Ndcg@10
509
+ - type: cosine_mrr@10
510
+ value: 0.9301560802395528
511
+ name: Cosine Mrr@10
512
+ - type: cosine_map@100
513
+ value: 0.9301560802395525
514
+ name: Cosine Map@100
515
+ ---
516
+
517
+ # SentenceTransformer based on Qwen/Qwen3-Embedding-0.6B
518
+
519
+ This is a [sentence-transformers](https://www.SBERT.net) model finetuned from [Qwen/Qwen3-Embedding-0.6B](https://huggingface.co/Qwen/Qwen3-Embedding-0.6B). It maps sentences & paragraphs to a 1024-dimensional dense vector space and can be used for semantic textual similarity, semantic search, paraphrase mining, text classification, clustering, and more.
520
+
521
+ ## Model Details
522
+
523
+ ### Model Description
524
+ - **Model Type:** Sentence Transformer
525
+ - **Base model:** [Qwen/Qwen3-Embedding-0.6B](https://huggingface.co/Qwen/Qwen3-Embedding-0.6B) <!-- at revision c54f2e6e80b2d7b7de06f51cec4959f6b3e03418 -->
526
+ - **Maximum Sequence Length:** 768 tokens
527
+ - **Output Dimensionality:** 1024 dimensions
528
+ - **Similarity Function:** Cosine Similarity
529
+ <!-- - **Training Dataset:** Unknown -->
530
+ <!-- - **Language:** Unknown -->
531
+ <!-- - **License:** Unknown -->
532
+
533
+ ### Model Sources
534
+
535
+ - **Documentation:** [Sentence Transformers Documentation](https://sbert.net)
536
+ - **Repository:** [Sentence Transformers on GitHub](https://github.com/huggingface/sentence-transformers)
537
+ - **Hugging Face:** [Sentence Transformers on Hugging Face](https://huggingface.co/models?library=sentence-transformers)
538
+
539
+ ### Full Model Architecture
540
+
541
+ ```
542
+ SentenceTransformer(
543
+ (0): Transformer({'max_seq_length': 768, 'do_lower_case': False, 'architecture': 'PeftModelForFeatureExtraction'})
544
+ (1): Pooling({'word_embedding_dimension': 1024, 'pooling_mode_cls_token': False, 'pooling_mode_mean_tokens': False, 'pooling_mode_max_tokens': False, 'pooling_mode_mean_sqrt_len_tokens': False, 'pooling_mode_weightedmean_tokens': False, 'pooling_mode_lasttoken': True, 'include_prompt': True})
545
+ (2): Normalize()
546
+ )
547
+ ```
548
+
549
+ ## Usage
550
+
551
+ ### Direct Usage (Sentence Transformers)
552
+
553
+ First install the Sentence Transformers library:
554
+
555
+ ```bash
556
+ pip install -U sentence-transformers
557
+ ```
558
+
559
+ Then you can load this model and run inference.
560
+ ```python
561
+ from sentence_transformers import SentenceTransformer
562
+
563
+ # Download from the 🤗 Hub
564
+ model = SentenceTransformer("sentence_transformers_model_id")
565
+ # Run inference
566
+ queries = [
567
+ "What is the proposed date/time for a meeting with Maintenance to review findings and strategize a remediation plan for OR wing HVAC fluctuations affecting post-op mobility protocols?",
568
+ ]
569
+ documents = [
570
+ 'Subject: HVAC System Issues Impacting OR Wing: Request for Collaborative Solution\nFrom: Dr. Susan L. Chang\nTo: Brian K. Lee\nDate: 2025-10-20\n\nHi Brian,\n\nThank you for raising this concern regarding the HVAC fluctuations in the OR wing. My team has indeed noticed some difficulties in maintaining prescribed post-operative mobility protocols due to variable temperatures, which can discourage early patient movement and affect our recovery benchmarks. I agree that partnering with Maintenance for timely remediation is essential; I can share specific observations from our unit that might help guide targeted improvements in the HVAC settings or scheduling.\n\nLet me know when would be best to meet with you and Maintenance so we can review findings and strategize a plan. Thanks again for the proactive outreach.\n\nBest,\nSusan',
571
+ "Subject: Payment Posting Discrepancy – Assistance Needed with Discharge Billing\nFrom: Isaiah T. Jackson\nTo: Taylor A. Richardson\nDate: 2025-10-30\n\nHi Taylor,\n\nThanks for bringing this to my attention. I've pulled the discharge plan and placement records and will cross-reference them with the insurance authorization to verify alignment. Once I have more clarity, I’ll coordinate with you and finance as needed to resolve any discrepancies—please hold off on correction for now. If I require any additional documentation, I’ll let you know.\n\nBest,\nIsaiah",
572
+ "Subject: Request for Conference Call Number\nFrom: Carol A. Campbell\nTo: Melissa K. King\nDate: 2025-10-27\n\nHi Melissa,\n\nI hope you're doing well. I am reaching out to request the conference call number for our upcoming credentialing review meeting scheduled later this week. Having the dial-in details ahead of time will help me circulate the information to all committee members and ensure we are fully prepared to discuss the physician files on the agenda. Please let me know at your earliest convenience if there are any specific protocols or security codes required for access.\n\nThank you very much for your assistance.\n\nBest regards,\nCarol",
573
+ ]
574
+ query_embeddings = model.encode_query(queries)
575
+ document_embeddings = model.encode_document(documents)
576
+ print(query_embeddings.shape, document_embeddings.shape)
577
+ # [1, 1024] [3, 1024]
578
+
579
+ # Get the similarity scores for the embeddings
580
+ similarities = model.similarity(query_embeddings, document_embeddings)
581
+ print(similarities)
582
+ # tensor([[0.7461, 0.0432, 0.0610]], dtype=torch.bfloat16)
583
+ ```
584
+
585
+ <!--
586
+ ### Direct Usage (Transformers)
587
+
588
+ <details><summary>Click to see the direct usage in Transformers</summary>
589
+
590
+ </details>
591
+ -->
592
+
593
+ <!--
594
+ ### Downstream Usage (Sentence Transformers)
595
+
596
+ You can finetune this model on your own dataset.
597
+
598
+ <details><summary>Click to expand</summary>
599
+
600
+ </details>
601
+ -->
602
+
603
+ <!--
604
+ ### Out-of-Scope Use
605
+
606
+ *List how the model may foreseeably be misused and address what users ought not to do with the model.*
607
+ -->
608
+
609
+ ## Evaluation
610
+
611
+ ### Metrics
612
+
613
+ #### Information Retrieval
614
+
615
+ * Dataset: `val_evaluation`
616
+ * Evaluated with [<code>InformationRetrievalEvaluator</code>](https://sbert.net/docs/package_reference/sentence_transformer/evaluation.html#sentence_transformers.evaluation.InformationRetrievalEvaluator)
617
+
618
+ | Metric | Value |
619
+ |:--------------------|:-----------|
620
+ | cosine_accuracy@1 | 0.8948 |
621
+ | cosine_accuracy@3 | 0.9583 |
622
+ | cosine_accuracy@5 | 0.98 |
623
+ | cosine_accuracy@10 | 1.0 |
624
+ | cosine_precision@1 | 0.8948 |
625
+ | cosine_precision@3 | 0.3194 |
626
+ | cosine_precision@5 | 0.196 |
627
+ | cosine_precision@10 | 0.1 |
628
+ | cosine_recall@1 | 0.8948 |
629
+ | cosine_recall@3 | 0.9583 |
630
+ | cosine_recall@5 | 0.98 |
631
+ | cosine_recall@10 | 1.0 |
632
+ | **cosine_ndcg@10** | **0.9472** |
633
+ | cosine_mrr@10 | 0.9302 |
634
+ | cosine_map@100 | 0.9302 |
635
+
636
+ <!--
637
+ ## Bias, Risks and Limitations
638
+
639
+ *What are the known or foreseeable issues stemming from this model? You could also flag here known failure cases or weaknesses of the model.*
640
+ -->
641
+
642
+ <!--
643
+ ### Recommendations
644
+
645
+ *What are recommendations with respect to the foreseeable issues? For example, filtering explicit content.*
646
+ -->
647
+
648
+ ## Training Details
649
+
650
+ ### Training Dataset
651
+
652
+ #### Unnamed Dataset
653
+
654
+ * Size: 2,394 training samples
655
+ * Columns: <code>sentence_0</code> and <code>sentence_1</code>
656
+ * Approximate statistics based on the first 1000 samples:
657
+ | | sentence_0 | sentence_1 |
658
+ |:--------|:----------------------------------------------------------------------------------|:-------------------------------------------------------------------------------------|
659
+ | type | string | string |
660
+ | details | <ul><li>min: 8 tokens</li><li>mean: 26.77 tokens</li><li>max: 63 tokens</li></ul> | <ul><li>min: 99 tokens</li><li>mean: 160.64 tokens</li><li>max: 399 tokens</li></ul> |
661
+ * Samples:
662
+ | sentence_0 | sentence_1 |
663
+ |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
664
+ | <code>What are the routine badge access needs for the phlebotomy team under the updated infection control protocol to prevent access-related delays in the patient observation wing?</code> | <code>Subject: Request for Assistance: Infection Control Protocol Update Impacting Phlebotomy Access<br>From: Paul R. Nelson<br>To: Carlos J. Rodriguez<br>Date: 2025-12-15<br><br>Hi Carlos,<br><br>I wanted to reach out regarding recent changes to our infection control protocols, which now require stricter badge access in certain areas, including the patient observation wing. We've had a few incidents where phlebotomy staff were delayed due to these new access restrictions. To ensure patient care isn't impacted, could you assist by identifying routine access needs for your team so we can adjust permissions accordingly? Please let me know if you or your team have experienced any specific challenges, and I’ll work to resolve these promptly.<br><br>Thanks for your cooperation,<br>Paul</code> |
665
+ | <code>Are there any specific legal/compliance issues to be addressed during the Emergency Preparedness Drill?</code> | <code>Subject: Re: Upcoming Hospital-wide Emergency Preparedness Drill – Participation Required<br>From: David R. Park<br>To: Richard T. Howard<br>Date: 2025-12-02<br><br>Hello Richard,<br><br>Thank you for the detailed announcement and for outlining the objectives of the upcoming Emergency Preparedness Drill. I appreciate the proactive approach to ensuring all staff are familiar with emergency protocols, especially with the simulation of both power and network outages. My team and I will review our current department safety procedures and ensure we are prepared to both participate in the drill and report any issues we discover. Please let me know if there are any specific compliance issues from the legal perspective you would like addressed during the exercise.<br><br>Best regards,<br>David R. Park</code> |
666
+ | <code>Quem é o responsável por fornecer o relatório de ultrassom de Miguel Silva para desbloquear a baixa de dívida incobrável?</code> | <code>Subject: Solicitação de apoio: aprovação de baixa de dívidas incobráveis<br>From: Rachel K. Martinez<br>To: Jasmine K. Patel<br>Date: 2025-10-27<br><br>Olá Jasmine,<br><br>Estou enfrentando dificuldades com a aprovação de uma baixa de dívida incobrável referente ao paciente do Pronto-Socorro. O sistema está bloqueando o processo devido à ausência de alguns documentos do setor de imagem. Você poderia, por favor, me ajudar a localizar ou encaminhar o relatório do ultrassom do paciente Miguel Silva? Precisamos desse documento para dar andamento à solicitação.<br><br>Agradeço pela agilidade!<br><br>Atenciosamente,<br>Rachel K. Martinez</code> |
667
+ * Loss: [<code>MultipleNegativesRankingLoss</code>](https://sbert.net/docs/package_reference/sentence_transformer/losses.html#multiplenegativesrankingloss) with these parameters:
668
+ ```json
669
+ {
670
+ "scale": 20.0,
671
+ "similarity_fct": "cos_sim",
672
+ "gather_across_devices": false
673
+ }
674
+ ```
675
+
676
+ ### Training Hyperparameters
677
+ #### Non-Default Hyperparameters
678
+
679
+ - `multi_dataset_batch_sampler`: round_robin
680
+
681
+ #### All Hyperparameters
682
+ <details><summary>Click to expand</summary>
683
+
684
+ - `do_predict`: False
685
+ - `eval_strategy`: no
686
+ - `prediction_loss_only`: True
687
+ - `per_device_train_batch_size`: 8
688
+ - `per_device_eval_batch_size`: 8
689
+ - `gradient_accumulation_steps`: 1
690
+ - `eval_accumulation_steps`: None
691
+ - `torch_empty_cache_steps`: None
692
+ - `learning_rate`: 5e-05
693
+ - `weight_decay`: 0.0
694
+ - `adam_beta1`: 0.9
695
+ - `adam_beta2`: 0.999
696
+ - `adam_epsilon`: 1e-08
697
+ - `max_grad_norm`: 1
698
+ - `num_train_epochs`: 3
699
+ - `max_steps`: -1
700
+ - `lr_scheduler_type`: linear
701
+ - `lr_scheduler_kwargs`: None
702
+ - `warmup_ratio`: None
703
+ - `warmup_steps`: 0
704
+ - `log_level`: passive
705
+ - `log_level_replica`: warning
706
+ - `log_on_each_node`: True
707
+ - `logging_nan_inf_filter`: True
708
+ - `enable_jit_checkpoint`: False
709
+ - `save_on_each_node`: False
710
+ - `save_only_model`: False
711
+ - `restore_callback_states_from_checkpoint`: False
712
+ - `use_cpu`: False
713
+ - `seed`: 42
714
+ - `data_seed`: None
715
+ - `bf16`: False
716
+ - `fp16`: False
717
+ - `bf16_full_eval`: False
718
+ - `fp16_full_eval`: False
719
+ - `tf32`: None
720
+ - `local_rank`: -1
721
+ - `ddp_backend`: None
722
+ - `debug`: []
723
+ - `dataloader_drop_last`: False
724
+ - `dataloader_num_workers`: 0
725
+ - `dataloader_prefetch_factor`: None
726
+ - `disable_tqdm`: False
727
+ - `remove_unused_columns`: True
728
+ - `label_names`: None
729
+ - `load_best_model_at_end`: False
730
+ - `ignore_data_skip`: False
731
+ - `fsdp`: []
732
+ - `fsdp_config`: {'min_num_params': 0, 'xla': False, 'xla_fsdp_v2': False, 'xla_fsdp_grad_ckpt': False}
733
+ - `accelerator_config`: {'split_batches': False, 'dispatch_batches': None, 'even_batches': True, 'use_seedable_sampler': True, 'non_blocking': False, 'gradient_accumulation_kwargs': None}
734
+ - `parallelism_config`: None
735
+ - `deepspeed`: None
736
+ - `label_smoothing_factor`: 0.0
737
+ - `optim`: adamw_torch_fused
738
+ - `optim_args`: None
739
+ - `group_by_length`: False
740
+ - `length_column_name`: length
741
+ - `project`: huggingface
742
+ - `trackio_space_id`: trackio
743
+ - `ddp_find_unused_parameters`: None
744
+ - `ddp_bucket_cap_mb`: None
745
+ - `ddp_broadcast_buffers`: False
746
+ - `dataloader_pin_memory`: True
747
+ - `dataloader_persistent_workers`: False
748
+ - `skip_memory_metrics`: True
749
+ - `push_to_hub`: False
750
+ - `resume_from_checkpoint`: None
751
+ - `hub_model_id`: None
752
+ - `hub_strategy`: every_save
753
+ - `hub_private_repo`: None
754
+ - `hub_always_push`: False
755
+ - `hub_revision`: None
756
+ - `gradient_checkpointing`: False
757
+ - `gradient_checkpointing_kwargs`: None
758
+ - `include_for_metrics`: []
759
+ - `eval_do_concat_batches`: True
760
+ - `auto_find_batch_size`: False
761
+ - `full_determinism`: False
762
+ - `ddp_timeout`: 1800
763
+ - `torch_compile`: False
764
+ - `torch_compile_backend`: None
765
+ - `torch_compile_mode`: None
766
+ - `include_num_input_tokens_seen`: no
767
+ - `neftune_noise_alpha`: None
768
+ - `optim_target_modules`: None
769
+ - `batch_eval_metrics`: False
770
+ - `eval_on_start`: False
771
+ - `use_liger_kernel`: False
772
+ - `liger_kernel_config`: None
773
+ - `eval_use_gather_object`: False
774
+ - `average_tokens_across_devices`: True
775
+ - `use_cache`: False
776
+ - `prompts`: None
777
+ - `batch_sampler`: batch_sampler
778
+ - `multi_dataset_batch_sampler`: round_robin
779
+ - `router_mapping`: {}
780
+ - `learning_rate_mapping`: {}
781
+
782
+ </details>
783
+
784
+ ### Training Logs
785
+ | Epoch | Step | Training Loss | val_evaluation_cosine_ndcg@10 |
786
+ |:------:|:----:|:-------------:|:-----------------------------:|
787
+ | 1.0 | 300 | - | 0.9461 |
788
+ | 1.6667 | 500 | 0.0168 | - |
789
+ | 2.0 | 600 | - | 0.9459 |
790
+ | 3.0 | 900 | - | 0.9472 |
791
+
792
+
793
+ ### Framework Versions
794
+ - Python: 3.12.12
795
+ - Sentence Transformers: 5.2.2
796
+ - Transformers: 5.0.0
797
+ - PyTorch: 2.9.0+cu128
798
+ - Accelerate: 1.12.0
799
+ - Datasets: 4.0.0
800
+ - Tokenizers: 0.22.2
801
+
802
+ ## Citation
803
+
804
+ ### BibTeX
805
+
806
+ #### Sentence Transformers
807
+ ```bibtex
808
+ @inproceedings{reimers-2019-sentence-bert,
809
+ title = "Sentence-BERT: Sentence Embeddings using Siamese BERT-Networks",
810
+ author = "Reimers, Nils and Gurevych, Iryna",
811
+ booktitle = "Proceedings of the 2019 Conference on Empirical Methods in Natural Language Processing",
812
+ month = "11",
813
+ year = "2019",
814
+ publisher = "Association for Computational Linguistics",
815
+ url = "https://arxiv.org/abs/1908.10084",
816
+ }
817
+ ```
818
+
819
+ #### MultipleNegativesRankingLoss
820
+ ```bibtex
821
+ @misc{henderson2017efficient,
822
+ title={Efficient Natural Language Response Suggestion for Smart Reply},
823
+ author={Matthew Henderson and Rami Al-Rfou and Brian Strope and Yun-hsuan Sung and Laszlo Lukacs and Ruiqi Guo and Sanjiv Kumar and Balint Miklos and Ray Kurzweil},
824
+ year={2017},
825
+ eprint={1705.00652},
826
+ archivePrefix={arXiv},
827
+ primaryClass={cs.CL}
828
+ }
829
+ ```
830
+
831
+ <!--
832
+ ## Glossary
833
+
834
+ *Clearly define terms in order to be accessible across audiences.*
835
+ -->
836
+
837
+ <!--
838
+ ## Model Card Authors
839
+
840
+ *Lists the people who create the model card, providing recognition and accountability for the detailed work that goes into its construction.*
841
+ -->
842
+
843
+ <!--
844
+ ## Model Card Contact
845
+
846
+ *Provides a way for people who have updates to the Model Card, suggestions, or questions, to contact the Model Card authors.*
847
+ -->
adapter_config.json ADDED
@@ -0,0 +1,46 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "alora_invocation_tokens": null,
3
+ "alpha_pattern": {},
4
+ "arrow_config": null,
5
+ "auto_mapping": null,
6
+ "base_model_name_or_path": "Qwen/Qwen3-Embedding-0.6B",
7
+ "bias": "none",
8
+ "corda_config": null,
9
+ "ensure_weight_tying": false,
10
+ "eva_config": null,
11
+ "exclude_modules": null,
12
+ "fan_in_fan_out": false,
13
+ "inference_mode": true,
14
+ "init_lora_weights": true,
15
+ "layer_replication": null,
16
+ "layers_pattern": null,
17
+ "layers_to_transform": null,
18
+ "loftq_config": {},
19
+ "lora_alpha": 16,
20
+ "lora_bias": false,
21
+ "lora_dropout": 0.05,
22
+ "megatron_config": null,
23
+ "megatron_core": "megatron.core",
24
+ "modules_to_save": null,
25
+ "peft_type": "LORA",
26
+ "peft_version": "0.18.1",
27
+ "qalora_group_size": 16,
28
+ "r": 8,
29
+ "rank_pattern": {},
30
+ "revision": null,
31
+ "target_modules": [
32
+ "o_proj",
33
+ "k_proj",
34
+ "v_proj",
35
+ "up_proj",
36
+ "q_proj",
37
+ "down_proj",
38
+ "gate_proj"
39
+ ],
40
+ "target_parameters": null,
41
+ "task_type": "FEATURE_EXTRACTION",
42
+ "trainable_token_indices": null,
43
+ "use_dora": false,
44
+ "use_qalora": false,
45
+ "use_rslora": false
46
+ }
adapter_model.safetensors ADDED
@@ -0,0 +1,3 @@
 
 
 
 
1
+ version https://git-lfs.github.com/spec/v1
2
+ oid sha256:e13217cebe4c89cb5238a96c57fea6dd044660f9202496c1935f5cd39e55daab
3
+ size 20234120
chat_template.jinja ADDED
@@ -0,0 +1,85 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {%- if tools %}
2
+ {{- '<|im_start|>system\n' }}
3
+ {%- if messages[0].role == 'system' %}
4
+ {{- messages[0].content + '\n\n' }}
5
+ {%- endif %}
6
+ {{- "# Tools\n\nYou may call one or more functions to assist with the user query.\n\nYou are provided with function signatures within <tools></tools> XML tags:\n<tools>" }}
7
+ {%- for tool in tools %}
8
+ {{- "\n" }}
9
+ {{- tool | tojson }}
10
+ {%- endfor %}
11
+ {{- "\n</tools>\n\nFor each function call, return a json object with function name and arguments within <tool_call></tool_call> XML tags:\n<tool_call>\n{\"name\": <function-name>, \"arguments\": <args-json-object>}\n</tool_call><|im_end|>\n" }}
12
+ {%- else %}
13
+ {%- if messages[0].role == 'system' %}
14
+ {{- '<|im_start|>system\n' + messages[0].content + '<|im_end|>\n' }}
15
+ {%- endif %}
16
+ {%- endif %}
17
+ {%- set ns = namespace(multi_step_tool=true, last_query_index=messages|length - 1) %}
18
+ {%- for message in messages[::-1] %}
19
+ {%- set index = (messages|length - 1) - loop.index0 %}
20
+ {%- if ns.multi_step_tool and message.role == "user" and not(message.content.startswith('<tool_response>') and message.content.endswith('</tool_response>')) %}
21
+ {%- set ns.multi_step_tool = false %}
22
+ {%- set ns.last_query_index = index %}
23
+ {%- endif %}
24
+ {%- endfor %}
25
+ {%- for message in messages %}
26
+ {%- if (message.role == "user") or (message.role == "system" and not loop.first) %}
27
+ {{- '<|im_start|>' + message.role + '\n' + message.content + '<|im_end|>' + '\n' }}
28
+ {%- elif message.role == "assistant" %}
29
+ {%- set content = message.content %}
30
+ {%- set reasoning_content = '' %}
31
+ {%- if message.reasoning_content is defined and message.reasoning_content is not none %}
32
+ {%- set reasoning_content = message.reasoning_content %}
33
+ {%- else %}
34
+ {%- if '</think>' in message.content %}
35
+ {%- set content = message.content.split('</think>')[-1].lstrip('\n') %}
36
+ {%- set reasoning_content = message.content.split('</think>')[0].rstrip('\n').split('<think>')[-1].lstrip('\n') %}
37
+ {%- endif %}
38
+ {%- endif %}
39
+ {%- if loop.index0 > ns.last_query_index %}
40
+ {%- if loop.last or (not loop.last and reasoning_content) %}
41
+ {{- '<|im_start|>' + message.role + '\n<think>\n' + reasoning_content.strip('\n') + '\n</think>\n\n' + content.lstrip('\n') }}
42
+ {%- else %}
43
+ {{- '<|im_start|>' + message.role + '\n' + content }}
44
+ {%- endif %}
45
+ {%- else %}
46
+ {{- '<|im_start|>' + message.role + '\n' + content }}
47
+ {%- endif %}
48
+ {%- if message.tool_calls %}
49
+ {%- for tool_call in message.tool_calls %}
50
+ {%- if (loop.first and content) or (not loop.first) %}
51
+ {{- '\n' }}
52
+ {%- endif %}
53
+ {%- if tool_call.function %}
54
+ {%- set tool_call = tool_call.function %}
55
+ {%- endif %}
56
+ {{- '<tool_call>\n{"name": "' }}
57
+ {{- tool_call.name }}
58
+ {{- '", "arguments": ' }}
59
+ {%- if tool_call.arguments is string %}
60
+ {{- tool_call.arguments }}
61
+ {%- else %}
62
+ {{- tool_call.arguments | tojson }}
63
+ {%- endif %}
64
+ {{- '}\n</tool_call>' }}
65
+ {%- endfor %}
66
+ {%- endif %}
67
+ {{- '<|im_end|>\n' }}
68
+ {%- elif message.role == "tool" %}
69
+ {%- if loop.first or (messages[loop.index0 - 1].role != "tool") %}
70
+ {{- '<|im_start|>user' }}
71
+ {%- endif %}
72
+ {{- '\n<tool_response>\n' }}
73
+ {{- message.content }}
74
+ {{- '\n</tool_response>' }}
75
+ {%- if loop.last or (messages[loop.index0 + 1].role != "tool") %}
76
+ {{- '<|im_end|>\n' }}
77
+ {%- endif %}
78
+ {%- endif %}
79
+ {%- endfor %}
80
+ {%- if add_generation_prompt %}
81
+ {{- '<|im_start|>assistant\n' }}
82
+ {%- if enable_thinking is defined and enable_thinking is false %}
83
+ {{- '<think>\n\n</think>\n\n' }}
84
+ {%- endif %}
85
+ {%- endif %}
config_sentence_transformers.json ADDED
@@ -0,0 +1,14 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "prompts": {
3
+ "query": "Instruct: Given a web search query, retrieve relevant passages that answer the query\nQuery:",
4
+ "document": ""
5
+ },
6
+ "default_prompt_name": null,
7
+ "similarity_fn_name": "cosine",
8
+ "model_type": "SentenceTransformer",
9
+ "__version__": {
10
+ "sentence_transformers": "5.2.2",
11
+ "transformers": "5.0.0",
12
+ "pytorch": "2.9.0+cu128"
13
+ }
14
+ }
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": 768,
3
+ "do_lower_case": false
4
+ }
tokenizer.json ADDED
@@ -0,0 +1,3 @@
 
 
 
 
1
+ version https://git-lfs.github.com/spec/v1
2
+ oid sha256:43f117cf004e0cf6b6a77ea42d686398dac7d22e4b15a89d3d1b2a0cc4d1c286
3
+ size 11423967
tokenizer_config.json ADDED
@@ -0,0 +1,30 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "add_prefix_space": false,
3
+ "backend": "tokenizers",
4
+ "bos_token": null,
5
+ "clean_up_tokenization_spaces": false,
6
+ "eos_token": "<|im_end|>",
7
+ "errors": "replace",
8
+ "extra_special_tokens": [
9
+ "<|im_start|>",
10
+ "<|im_end|>",
11
+ "<|object_ref_start|>",
12
+ "<|object_ref_end|>",
13
+ "<|box_start|>",
14
+ "<|box_end|>",
15
+ "<|quad_start|>",
16
+ "<|quad_end|>",
17
+ "<|vision_start|>",
18
+ "<|vision_end|>",
19
+ "<|vision_pad|>",
20
+ "<|image_pad|>",
21
+ "<|video_pad|>"
22
+ ],
23
+ "is_local": false,
24
+ "model_max_length": 131072,
25
+ "model_specific_special_tokens": {},
26
+ "pad_token": "<|endoftext|>",
27
+ "split_special_tokens": false,
28
+ "tokenizer_class": "Qwen2Tokenizer",
29
+ "unk_token": null
30
+ }