LFM2-350M-Extract

Based on LFM2-350M, LFM2-350M-Extract is designed to extract important information from a wide variety of unstructured documents (such as articles, transcripts, or reports) into structured outputs like JSON, XML, or YAML.

Use cases:

• Extracting invoice details from emails into structured JSON.
• Converting regulatory filings into XML for compliance systems.
• Transforming customer support tickets into YAML for analytics pipelines.
• Populating knowledge graphs with entities and attributes from unstructured reports.

You can find more information about other task-specific models in this blog post.

📄 Model details

Generation parameters: We strongly recommend using greedy decoding with a temperature=0.

System prompt: If no system prompt is provided, the model will default to JSON outputs. We recommend providing a system prompt with a specific format (JSON, XML, or YAML) and a given schema to improve accuracy (see the following example).

Supported languages: English, Arabic, Chinese, French, German, Japanese, Korean, Portuguese, and Spanish.

Chat template: LFM2 uses a ChatML-like chat template as follows:

<|startoftext|><|im_start|>system
Return data as a JSON object with the following schema:\n[...]<|im_end|>
<|im_start|>user
Caenorhabditis elegans is a free-living transparent nematode about 1 mm in length that lives in temperate soil environments.<|im_end|>
<|im_start|>assistant
{
"species": "C. elegans",
"genus": "Caenorhabditis",
"description": "A free-living transparent nematode about 1 mm in length that lives in temperate soil environments.",
[...]{<|im_end|>

You can automatically apply it using the dedicated .apply_chat_template() function from Hugging Face transformers.

[!WARNING] ⚠️ The model is intended for single-turn conversations.

The data used for training these models was primarily synthetic, which allowed us to ensure a diverse data mix. We used a range of document types, domains, styles, lengths, and languages. We also varied the density and distribution of relevant text in the documents. In some cases, the extracted information was clustered in one part of the document; in others, it’s spread throughout. We applied the same approach of ensuring diversity when creating synthetic user requests and designing the structure of the model outputs. The data generation process underwent many iterations, incorporating ideas and feedback from across the Liquid AI team.

📈 Performance

We evaluated LFM2-Extract on a dataset of 5,000 documents, covering over 100 topics with a mix of writing styles, ambiguities, and formats. We used a combination of five metrics to capture a balanced view on syntax, accuracy, and faithfulness:

• Syntax score: Checks whether outputs parse cleanly as valid JSON, XML, or YAML.
• Format accuracy: Verifies that outputs match the requested format (e.g., JSON when JSON is requested).
• Keyword faithfulness: Measures whether values in the structured output actually appear in the input text.
• Absolute scoring: A judge LLM scores quality on a 1-5 scale, assessing completeness and correctness of extractions.
• Relative scoring: We ask a judge LLM to choose the best answer between the extraction model’s output and the ground-truth answer.

LFM2-350M-Extract outperforms Gemma 3 4B at this task, a model more than 11x its size.

🏃 How to run

• Hugging Face: LFM2-350M
• llama.cpp: LFM2-350M-Extract-GGUF
• LEAP: LEAP model library

You can use the following Colab notebooks for easy inference and fine-tuning:

📬 Contact

• Got questions or want to connect? Join our Discord community
• If you are interested in custom solutions with edge deployment, please contact our sales team.

Citation

@article{liquidai2025lfm2,
 title={LFM2 Technical Report},
 author={Liquid AI},
 journal={arXiv preprint arXiv:2511.23404},
 year={2025}
}