Model Card for GaMS-27B-Instruct

GaMS-2B, GaMS-9B and GaMS-27B represent new improved and larger models of the GaMS (Generative Model for Slovene) familly. The models are based on Google's Gemma 2 familly and continually pretrained on Slovene, English and some portion of Croatian, Serbian and Bosnian corpora.

This is the SFT version of GaMS-27B model

Acknowledgment

The model was developed within the PoVeJMo research program (Adaptive Natural Language Processing with Large Language Models), particularly within the research project titled SloLLaMai -- Open-access computationally efficient models for Slovenian. The program is funded within the Recovery and Resilience Plan by the Slovenian Research and Innovation Agency (ARIS) and NextGenerationEU. The authors also acknowledge the financial support from the Slovenian Research and Innovation Agency (research core funding No. P6-0411 -- Language Resources and Technologies for Slovene).

We thank everyone who worked on data collection and preparation, enabling us to train our model. Special thanks go to Nikola Ljubešić, Taja Kuzman, Tjaša Arčon, Jaka Čibej, Simon Krek, Tomaž Erjavec, Iztok Kosem and Tomaž Savodnik.

Basic information

• Developed by: team of researchers at the University of Ljubljana, Faculty for Computer and Information Science. Team members: Domen Vreš, Iztok Lebar Bajec, Tjaša Arčon, Gašper Jelovčan and Marko Robnik-Šikonja.
• Languages: Slovene, English (primary), Croatian, Bosnian and Serbian (secondary). The model might also work for other languages supported by Gemma 2, even though it was not continually pretrained on them.
• Base model: cjvt/GaMS-27B
• License: Gemma

Usage

The model can be run through pipeline API using the following code:

from transformers import pipeline

model_id = "cjvt/GaMS-27B-Instruct"

pline = pipeline(
    "text-generation",
    model=model_id,
    device_map="cuda" # replace with "mps" to run on a Mac device
)

# Example of response generation
message = [{"role": "user", "content": "Kateri je najpomembnejši dogodek v slovenski zgodovini?"}]
response = pline(message, max_new_tokens=512)
print("Model's response:", response[0]["generated_text"][-1]["content"])

# Example of conversation chain
new_message = response[0]["generated_text"]
new_message.append({"role": "user", "content": "Lahko bolj podrobno opišeš ta dogodek?"})
response = pline(new_message, max_new_tokens=1024)
print("Model's response:", response[0]["generated_text"][-1]["content"])

For multi GPU inference set the device_map to auto:

from transformers import pipeline

model_id = "cjvt/GaMS-27B-Instruct"

pline = pipeline(
    "text-generation",
    model=model_id,
    device_map="auto"
)

# Example of response generation
message = [{"role": "user", "content": "Kateri je najpomembnejši dogodek v slovenski zgodovini?"}]
response = pline(message, max_new_tokens=512)
print("Model's response:", response[0]["generated_text"][-1]["content"])

# Example of conversation chain
new_message = response[0]["generated_text"]
new_message.append({"role": "user", "content": "Lahko bolj podrobno opišeš ta dogodek?"})
response = pline(new_message, max_new_tokens=1024)
print("Model's response:", response[0]["generated_text"][-1]["content"])

Data

CPT Data

Model was continually pre-trained in two stages. In the first stage, parallel English-Slovene (and Croatian in some cases) corpora was used to align the languages. In the second stage, the model was trained on separate English, Slovene, Croatian, Bosnian and Serbian corpora.

Parallel alignment corpora

Explanation of each alignment level:

• Document level: Parallel documents were concatenated into a single document
• Separate documents: Parallel documents were not explicitly aligned
• Paragraph level: Paragraphs of parallel documents were concatenated (the first paragraph of Slovene/English document was followed by the first paragraph in the other language, which was then followed by the second paragraph in the first language and so on)

Second stage corpora

Remarks:

• The following corpora was excluded from MetaFida: dgt15_sl, classlawiki_sl, tweet_sl, janes_tweet, janes_forum, janes_news
• Serbian Wikipedia was converted from Cyrillic to Latin

SFT Data

Our training data for SFT consisted out of approximately 25.000 training and 1500 validation examples. The dataset was a mixture of following datasets:

• GaMS-Instruct-GEN 1.0
• GaMS-Instruct-DH 1.0: 3000 randomly selected examples were chosen from this dataset
• GaMS-Instruct-MED 1.0: 3000 randomly selected examples were chosen from this dataset
• Parallel corpus EN-SL RSDO4 2.0: additional filtering was done on this corpus. First we ran FastText language identification using NeMo Curator and kept only the examples were source was detected as English and target as Slovene. Next, we ran COMET model to evaluate translations. We kept only the examples with COMET scores higher than 0.945 (approximatelly 8000 examples).
• Aya Dataset: only English and Serbian examples were taken from this dataset. Serbian examples were converted from Cyrillic to Latin.
• Math competitions: We took PDFs from Slovene national math competitions between years 2001 and 2010. We extracted text from PDFs using olmOCR and manually corrected the extracted text. This gave us around 150 solved math problems.

Training

The model was trained on the Booster partition of Leonardo HPC.

CPT

We continually pretrained the model using NVIDIA NeMo 2.0 framework. The model was trained in BF16-Mixed precision using tensor parallelism across 8 GPUs, sequence parallelism, and activation recomputation. The model was trained across 32 nodes, each containing 4 A100 64GB GPUs. The parallel alignment training took approximately 8 hours and second stage took approximately 110 hours.

The model was trained using a cosine learning rate scheduler with linear warmup and the following hyperparameters.

Parallel alignment:

• warmup steps: 150
• minimal learning rate: 5e-6
• maximal learning rate: 2e-5
• constant steps: 0
• batch size: 512 (4 million tokens)

Second stage:

• warmup steps: 500
• minimal learning rate: 5e-6
• maximal learning rate: 5e-5
• constant steps: 100
• batch size: 512 (4 million tokens)

SFT

As a contrast to 2B and 9B models, the 27B was supervised fine-tuned using NeMo framework, which enables easier scalng. The model was trained in BF16 precision, using tensor parallelism to split it across 4 GPUs, sequence parallelism, and activation recomputation. The model was trained on 8 nodes with 4 A100 64 GB GPU.

The model was tuned using a cosine learning rate scheduler with linear warmup and the following hyperparameters:

• number of epochs: training was done on 5 epochs, but the best performing model according to validation loss was obtained after the second epoch, so we kept that model
• batch size: 128
• warmup steps: 150
• minimal learning rate: 1e-8
• maximal learning rate: 5e-6
• constant steps: 0

Evaluation

The models were evaluated using Slovene SuperGLUE collection of classification tasks on SloBench. Instruct version of the model was also evaluated on translation from English to Slovene and from Slovene to English. Additionally, we evaluated our models on Slovenian-LLM-Eval.

Code for evaluation:

• SloBench tasks
• Slovenian-LLM-Eval

Slovenian-LLM-Eval results

Comparison between GaMS models, base Gemma 2 models and SlovenianGPT (open source model for Slovene based on Mistral 7B) is shown in the figure below. All models were evaluated in 0-shot scenario.

Slobench Results

GaMS 2B, 9B, 27B and 27B-Instruct models were evaluated in 3-shot scenario, except for MultiRC and translation tasks, where 0-shot was used. GaMS-2B-Instruct and GaMS-9B-Instruct were evaluated in 0-shot scenarion on all tasks. We used guided decoding to ensure the correct format of the responses.

Slovene SuperGLUE

English to Slovene translation (first 11 models on the benchmark)

Slovene to English translation (first 10 models on the benchmark)

Usage and Limitations (taken from Gemma 2)

These models have certain limitations that users should be aware of.

Intended Usage

Open Large Language Models (LLMs) have a wide range of applications across various industries and domains. The following list of potential uses is not comprehensive. The purpose of this list is to provide contextual information about the possible use-cases that the model creators considered as part of model training and development.

• Content Creation and Communication
  • Text Generation: These models can be used to generate creative text formats such as poems, scripts, code, marketing copy, and email drafts.
  • Chatbots and Conversational AI: Power conversational interfaces for customer service, virtual assistants, or interactive applications.
  • Text Summarization: Generate concise summaries of a text corpus, research papers, or reports.
• Research and Education
  • Natural Language Processing (NLP) Research: These models can serve as a foundation for researchers to experiment with NLP techniques, develop algorithms, and contribute to the advancement of the field.
  • Language Learning Tools: Support interactive language learning experiences, aiding in grammar correction or providing writing practice.
  • Knowledge Exploration: Assist researchers in exploring large bodies of text by generating summaries or answering questions about specific topics.

Limitations

• Training Data
  • The quality and diversity of the training data significantly influence the model's capabilities. Biases or gaps in the training data can lead to limitations in the model's responses.
  • The scope of the training dataset determines the subject areas the model can handle effectively.
• Context and Task Complexity
  • LLMs are better at tasks that can be framed with clear prompts and instructions. Open-ended or highly complex tasks might be challenging.
  • A model's performance can be influenced by the amount of context provided (longer context generally leads to better outputs, up to a certain point).
• Language Ambiguity and Nuance
  • Natural language is inherently complex. LLMs might struggle to grasp subtle nuances, sarcasm, or figurative language.
• Factual Accuracy
  • LLMs generate responses based on information they learned from their training datasets, but they are not knowledge bases. They may generate incorrect or outdated factual statements.
• Common Sense
  • LLMs rely on statistical patterns in language. They might lack the ability to apply common sense reasoning in certain situations.

Ethical Considerations and Risks

The development of large language models (LLMs) raises several ethical concerns. In creating an open model, we have carefully considered the following:

• Bias and Fairness
  • LLMs trained on large-scale, real-world text data can reflect socio-cultural biases embedded in the training material. These models underwent careful scrutiny, input data pre-processing described and posterior evaluations reported in this card.
• Misinformation and Misuse
  • LLMs can be misused to generate text that is false, misleading, or harmful.
  • Guidelines are provided for responsible use with the model, see the [Responsible Generative AI Toolkit][rai-toolkit].
• Transparency and Accountability:
  • This model card summarizes details on the models' architecture, capabilities, limitations, and evaluation processes.
  • A responsibly developed open model offers the opportunity to share innovation by making LLM technology accessible to developers and researchers across the AI ecosystem.

Risks identified and mitigations:

• Perpetuation of biases: It's encouraged to perform continuous monitoring (using evaluation metrics, human review) and the exploration of de-biasing techniques during model training, fine-tuning, and other use cases.
• Generation of harmful content: Mechanisms and guidelines for content safety are essential. Developers are encouraged to exercise caution and implement appropriate content safety safeguards based on their specific product policies and application use cases.
• Misuse for malicious purposes: Technical limitations and developer and end-user education can help mitigate against malicious applications of LLMs. Educational resources and reporting mechanisms for users to flag misuse are provided. Prohibited uses of Gemma models are outlined in the [Gemma Prohibited Use Policy][prohibited-use].
• Privacy violations: Models were trained on data filtered for removal of PII (Personally Identifiable Information). Developers are encouraged to adhere to privacy regulations with privacy-preserving techniques.