afalaudn / gemma-embedding-ft3

SentenceTransformer based on unsloth/embeddinggemma-300m

This is a sentence-transformers model finetuned from unsloth/embeddinggemma-300m . It maps sentences & paragraphs to a 768-dimensional dense vector space and can be used for semantic textual similarity, semantic search, paraphrase mining, text classification, clustering, and more.

Model Details

Model Description

• Model Type: Sentence Transformer
• Base model: unsloth/embeddinggemma-300m
• Maximum Sequence Length: 768 tokens
• Output Dimensionality: 768 dimensions
• Similarity Function: Cosine Similarity

Model Sources

• Documentation: Sentence Transformers Documentation
• Repository: Sentence Transformers on GitHub
• Hugging Face: Sentence Transformers on Hugging Face

Full Model Architecture

SentenceTransformer(
  (0): Transformer({'max_seq_length': 768, 'do_lower_case': False, 'architecture': 'Gemma3TextModel'})
  (1): Pooling({'word_embedding_dimension': 768, 'pooling_mode_cls_token': False, 'pooling_mode_mean_tokens': True, 'pooling_mode_max_tokens': False, 'pooling_mode_mean_sqrt_len_tokens': False, 'pooling_mode_weightedmean_tokens': False, 'pooling_mode_lasttoken': False, 'include_prompt': True})
  (2): Dense({'in_features': 768, 'out_features': 3072, 'bias': False, 'activation_function': 'torch.nn.modules.linear.Identity'})
  (3): Dense({'in_features': 3072, 'out_features': 768, 'bias': False, 'activation_function': 'torch.nn.modules.linear.Identity'})
  (4): Normalize()
)

Usage

Direct Usage (Sentence Transformers)

First install the Sentence Transformers library:

pip install -U sentence-transformers

Then you can load this model and run inference.

from sentence_transformers import SentenceTransformer

# Download from the 🤗 Hub
model = SentenceTransformer("afalaudn/gemma-embedding-ft3")
# Run inference
sentences = [
    "Retrieve the names of all patients who have a 'MedicalRecordStatusId' indicating 'Active' in their PatientOrganization record and have received an invoice from any organization in the current month.",
    "Primary reference table storing the comprehensive master profiles of all patients registered in the hospital system. It contains critical demographic data including Name, Medical Record Number (MrNo), Birth Date, Gender (SexId), Address, Contact Information (Phone, Email), and Identification details (National ID, Passport). It also tracks patient status (Active/Merged/Deceased) and links to external Payer/Insurance information. Use this table to identify unique patients, retrieve contact details for notifications, segment patient populations by demographics, or link clinical transactions to specific individuals. Note: This table represents the 'Golden Record' of a patient's identity; historical changes might be tracked in audit logs, but this table holds the current state.",
    'Primary reference table defining the standard set of religions and spiritual beliefs for patient demographic data. It contains codes and names for major religions such as Islam, Christian, Catholic, Hindu, and Buddhist. **Use this table to** interpret the `ReligionId` from patient master data to standardize demographic reporting or analyze patient spiritual care needs. **Note: This table lists the CATEGORIES of religion only, not the religious affiliation of individual patients.**',
]
embeddings = model.encode(sentences)
print(embeddings.shape)
# [3, 768]

# Get the similarity scores for the embeddings
similarities = model.similarity(embeddings, embeddings)
print(similarities)
# tensor([[ 1.0000,  0.6662, -0.1269],
#         [ 0.6662,  1.0000,  0.1456],
#         [-0.1269,  0.1456,  1.0000]])

Evaluation

Metrics

Information Retrieval

• Evaluated with InformationRetrievalEvaluator

Training Details

Training Dataset

Unnamed Dataset

• Size: 1,340 training samples
• Columns: anchor , positive , and negative
• Approximate statistics based on the first 1000 samples:

  	anchor	positive	negative
  type	string	string	string
  details	min: 10 tokens mean: 35.94 tokens max: 82 tokens	min: 63 tokens mean: 129.79 tokens max: 171 tokens	min: 63 tokens mean: 112.02 tokens max: 175 tokens

• Samples:

  anchor	positive	negative
  What is the total number of patient admissions that resulted in a 'Recovered' discharge condition for each organization in 2023?	Operational transaction table recording every patient registration and visit event at the hospital. This table consolidates patient demographics, visit types (Inpatient, Outpatient, Emergency), primary and referral doctors, payer/insurance eligibility, and critical timelines (Admission and Discharge dates). Use this table to calculate patient census, Average Length of Stay (ALOS), track patient flow, or analyze admission volume by doctor or department. Note: This table focuses on administrative registration and billing initiation; it does not contain detailed clinical notes, specific lab results, or medication prescriptions. When analyzing patient administrative inflow and outflow data, this table is the primary and essential source for all patient visit metrics.	This reference table defines the high-level administrative outcomes of a patient's discharge process. It includes standard codes, English names, and Indonesian translations (LocalName) such as 'Discharged' (Pulang) and 'Cancelled' (Batal). Use this table to categorize the final resolution of a hospital visit, determining if a patient successfully left care or if the discharge process was voided. Note: This table tracks the administrative status of the discharge event itself, not the clinical medical condition (e.g., improved, cured) or the specific reason for discharge.
  Retrieve the AdmissionNo and InvoiceNo for all admissions where the patient was not previously registered (Admission.IsPatientRegistered = 0) and the invoice was issued by an organization with an IsActive status of 'true'.	Operational transaction table (Financial Log) recording the header-level details of patient invoices and billing events. This table captures the financial breakdown of a visit, distinguishing between Patient responsibility (Out-of-pocket) and Payer responsibility (Insurance/Corporate Coverage), including Gross Amounts, Discounts, Taxes, and Net Payable values. Use this table to analyze hospital revenue streams, track Accounts Receivable (AR), monitor billing cancellations, or calculate the financial yield per admission. Note: This is the Invoice HEADER table containing total values; it does not typically list the specific individual line items (drugs, labs, services) charged within the bill. For any financial analysis related to hospital revenue, Payments, Accounts Receivable (AR), billing breakdowns, or insurance claims, this invoice header table is the definitive starting point.	Operational transaction table recording formal requests to retrieve physical medical record folders from the Medical Records Department (MRD). It tracks the details of the request, including the specific patient file ( PatientOrganizationId ), the requesting doctor ( DoctorUserId ), the intended destination ( FolderDestinationTypeId ), and the urgency or type of request ( FolderRequestTypeId ). Use this table to measure MRD service levels, track the volume of physical file retrievals, or audit the reasons for accessing physical records. Note: This tracks the request for a physical object, NOT the digital access to the EMR or the actual content of the medical record.
  What is the average age of patients with 'Active' status who had an 'Inpatient' admission in 2024, compared to those with 'Inactive' status?	Operational transaction table recording every patient registration and visit event at the hospital. This table consolidates patient demographics, visit types (Inpatient, Outpatient, Emergency), primary and referral doctors, payer/insurance eligibility, and critical timelines (Admission and Discharge dates). Use this table to calculate patient census, Average Length of Stay (ALOS), track patient flow, or analyze admission volume by doctor or department. Note: This table focuses on administrative registration and billing initiation; it does not contain detailed clinical notes, specific lab results, or medication prescriptions. When analyzing patient administrative inflow and outflow data, this table is the primary and essential source for all patient visit metrics.	Operational transaction table recording the official event of a patient leaving the hospital (Discharge). It captures the precise discharge timestamp, the patient's condition upon exit (e.g., Recovered, Improved), and the type of discharge (e.g., Medical Consent, Transfer) linked to their Admission. Use this table to calculate Length of Stay (LOS), analyze clinical outcomes, or track bed turnover rates. Note: This table signifies the physical or administrative end of a visit; it does NOT contain the final invoice amount, though it triggers the billing closure process.

• Loss: TripletLoss with these parameters:

  {
      "distance_metric": "TripletDistanceMetric.COSINE",
      "triplet_margin": 1
  }
  

Evaluation Dataset

Unnamed Dataset

• Size: 335 evaluation samples
• Columns: anchor , positive , and negative
• Approximate statistics based on the first 335 samples:

  	anchor	positive	negative
  type	string	string	string
  details	min: 10 tokens mean: 35.25 tokens max: 77 tokens	min: 63 tokens mean: 128.23 tokens max: 171 tokens	min: 63 tokens mean: 111.21 tokens max: 171 tokens

• Samples:

  anchor	positive	negative
  Retrieve the admission number, invoice number, and admission type name for all admissions that occurred in January 2023 and had an invoice issued within 7 days of the admission date.	Primary reference table defining the high-level classification of patient visits and hospital service lines. Contains standard categories including Inpatient (Hospitalization), Outpatient (Clinical visits), Emergency (ER), and Health Checkups (MCU). Use this table to group patient volume by service type, filter admission logs, or analyze revenue streams by visit category. Note: This is a static lookup list defining the 'Types' of visits; it does not contain actual patient visit transaction records.	Operational transaction table that records the detailed line items of an inventory stock take event. It captures the specific ItemId being counted, the quantity recorded in the system ( SystemStockQuantity ), the actual PhysicalStockQuantity counted, and the resulting VarianceStockQuantity . For batch-tracked items, it also includes BatchNo and ExpiryDate . Use this table to analyze inventory discrepancies, identify expired or expiring stock during a count, or audit the accuracy of stock records for a specific item. Note: This table contains the detailed results of a specific stock count event ; it does NOT provide the real-time inventory balance of an item.
  What is the total number of invoices and the total value of these invoices issued in Q1 2024 for female patients whose current status is 'Active'?	Primary reference table defining the validity and lifecycle status of a patient's master record. Contains status codes such as 'Active', 'Inactive', and 'Deceased' to classify patient accounts. Use this table to look up status meanings or filter patient queries based on their account state (e.g., excluding deceased patients from active lists). Note: This is a lookup dictionary for status codes, NOT a transaction log of status changes for specific patients.	Operational snapshot table that holds the single, current financial state of a patient at a specific hospital unit. Unlike a transaction log, this table does not track history; it contains only the final calculated totals: BalanceAmount (Total AR/Debt outstanding) and DepositBalanceAmount (Total Advance Payment available). Use this table for quick validation of whether a patient can be discharged, checking total debt before billing, or viewing available deposit funds. Concept: Think of this as the 'ATM Screen Balance' showing only the final amount available right now.
  Tampilkan data Master Data Hospital Rooms (Room)	Primary reference table defining individual patient rooms within a hospital ward. It contains specific room codes and names, linking each room to its parent Ward ( WardId ) and hospital branch ( OrganizationId ), representing the most granular level of inpatient location master data. Use this table to map RoomId from bed management or admission transactions to a specific room number, analyze room availability, or manage hospital accommodation resources. Note: This table lists the physical room definitions only, not the individual beds within a room or the real-time patient occupancy status.	Operational transaction table recording the historical log of bed movements and transfers within the hospital organization. This table captures the exact timestamp of transfer events and identifies the specific Bed asset involved. Use this table to track the history of bed locations, audit bed usage timelines, or monitor the frequency of bed transfers. Note: This table focuses on the physical Bed entity's movement timeline; based on the provided columns, it does not explicitly contain Patient or Admission IDs.

• Loss: TripletLoss with these parameters:

  {
      "distance_metric": "TripletDistanceMetric.COSINE",
      "triplet_margin": 1
  }
  

Training Hyperparameters

Non-Default Hyperparameters

• eval_strategy : steps
• per_device_train_batch_size : 16
• per_device_eval_batch_size : 16
• gradient_accumulation_steps : 4
• learning_rate : 2e-05
• num_train_epochs : 5
• warmup_ratio : 0.1
• fp16 : True
• load_best_model_at_end : True
• prompts : {'anchor': ' ', 'positive': '', 'negative': ''}
• batch_sampler : no_duplicates

All Hyperparameters

Training Logs

Framework Versions

• Python: 3.12.12
• Sentence Transformers: 5.2.2
• Transformers: 4.57.6
• PyTorch: 2.10.0+cu128
• Accelerate: 1.12.0
• Datasets: 4.3.0
• Tokenizers: 0.22.2

Citation

BibTeX

Sentence Transformers

@inproceedings{reimers-2019-sentence-bert,
    title = "Sentence-BERT: Sentence Embeddings using Siamese BERT-Networks",
    author = "Reimers, Nils and Gurevych, Iryna",
    booktitle = "Proceedings of the 2019 Conference on Empirical Methods in Natural Language Processing",
    month = "11",
    year = "2019",
    publisher = "Association for Computational Linguistics",
    url = "https://arxiv.org/abs/1908.10084",
}

TripletLoss

@misc{hermans2017defense,
    title={In Defense of the Triplet Loss for Person Re-Identification},
    author={Alexander Hermans and Lucas Beyer and Bastian Leibe},
    year={2017},
    eprint={1703.07737},
    archivePrefix={arXiv},
    primaryClass={cs.CV}
}