GLiNER2.5-multi-Decide

The 287M multilingual classification model in the GLiNER2.5 family. Pass any label set at call time: intent, routing, sentiment, priority, policy, and multi-label tags, in a single forward pass. No prompt template. No generated tokens. Load it with AutoExtractor and ship it locally.

Use it when the text is not English. A single call can score several heads at once. Single-label tasks return one string. Multi-label tasks return every label above the threshold.

Benchmark

Exact-match accuracy on fastino/fast-decisions: 17 domains, 300 held-out examples each, with the same text and candidate labels for every model.

The suite is English. Use GLiNER2.5-Decide for English-only text; use this model when the input is multilingual. Domain and label details are on the dataset card.

This release is not a general-purpose model. It does not reason, explain, or answer open questions. It is a specialist for operational decisions: customer and banking intent, travel and clinic requests, review sentiment, document type, email and ticket routing, human handoff, agent completion, moderation, severity, urgency, and spam. The same call also answers a question about a passage, classifies a book, uses labels that carry a description, and scores an ordinal scale.

Outputs below are potential results for these inputs. They show the shape classify_text returns.

Install

pip install "gliner2[local]"

from gliner2 import AutoExtractor

model = AutoExtractor.from_pretrained("fastino/GLiNER2.5-multi-Decide")

Examples

Customer support intent

Route a live message before a human ever sees it. Refunds, cancellations, login failures, and shipping delays share one inbox and one label set. Decide picks the action the queue should take, so the right workflow starts on the first turn.

model.classify_text(
    "My subscription renewed on April 15 for ¥5,400 after the service was already down. Can I get that charge refunded?",
    {"intent": [
        "order_status", "refund_request", "cancel_subscription", "update_payment",
        "login_problem", "shipping_delay", "bug_report", "speak_to_human", "other",
    ]},
)

Potential output:

{"intent": "refund_request"}

Banking request

A single customer message often mixes a failed payment, a beneficiary change, and a fee question. The label set is the product catalog: transfers, cards, fraud, mortgages. The model maps the utterance onto the operation the core system should open.

model.classify_text(
    "The transfer I sent this morning is still pending, and I think I used the wrong sort code. Can you stop it and add Emily as the beneficiary instead?",
    {"intent": [
        "transfer_pending", "transfer_cancel", "beneficiary_add", "card_lost",
        "balance_inquiry", "fraud_report", "mortgage_application", "fee_explanation",
    ]},
)

Potential output:

{"intent": "transfer_cancel"}

Travel request

Booking, changing, cancelling, and seat requests look similar in free text and trigger different inventory calls. Use this when a chat or email has to become a structured booking action without a form.

model.classify_text(
    "I need to move my Friday flight to Paris to Saturday morning, same cabin, and keep the aisle seat if you can.",
    {"request": ["book", "change", "cancel", "status", "seat_change", "refund", "baggage"]},
)

Potential output:

{"request": "change"}

Clinic request

Patients describe symptoms and the thing they want in the same sentence: an appointment, a refill, a result, a referral. Front-desk routing needs that distinction before anyone is put on a schedule.

model.classify_text(
    "The rash came back after the antibiotics finished. Can I get a same-week appointment with dermatology, or should I just refill the cream?",
    {"request": [
        "book_appointment", "refill_prescription", "test_results",
        "referral", "billing_question", "cancel_appointment",
    ]},
)

Potential output:

{"request": "book_appointment"}

Review sentiment

Star ratings hide mixed reviews. A product can be praised and rejected in one paragraph. A four-way sentiment label is what a dashboard, a reply policy, or a ranking feature actually needs.

model.classify_text(
    "Battery dies before lunch, but the keyboard and the screen are the best I have used on a laptop.",
    {"sentiment": ["positive", "negative", "mixed", "neutral"]},
)

Potential output:

{"sentiment": "mixed"}

Product aspects

Sentiment says the review is mixed. Aspects say why: battery, keyboard, screen. Several labels apply at once, so this head is multi-label. That is the input to aspect-level analytics and to a reply that mentions the right part of the product.

model.classify_text(
    "Battery dies before lunch, but the keyboard and the screen are the best I have used on a laptop.",
    {"aspects": {
        "labels": ["battery", "keyboard", "screen", "camera", "price", "support"],
        "multi_label": True,
        "cls_threshold": 0.4,
    }},
)

Potential output:

{"aspects": ["battery", "keyboard", "screen"]}

News topic

Wire copy, alerts, and scraped headlines have to land in a section before they are ranked or summarized. The label set is the section list of the product, not a fixed taxonomy baked into the model.

model.classify_text(
    "The central bank held rates and said inflation is still above target, pushing bank stocks lower in afternoon trading.",
    {"topic": ["politics", "business", "sports", "science", "entertainment", "world"]},
)

Potential output:

{"topic": "business"}

Document type

Inboxes and shared drives mix invoices, contracts, resumes, and notes. Classifying the document is the gate in front of extraction: an invoice goes to payables, a contract goes to review, a resume goes to screening.

model.classify_text(
    "INVOICE 1842\nBill to: Northstar QA\nAmount due: 2,400 USD\nDue: 30 April 2026\nWire instructions are on page 2.",
    {"document_type": ["invoice", "receipt", "contract", "resume", "support_email", "meeting_notes"]},
)

Potential output:

{"document_type": "invoice"}

Email triage

A shared mailbox needs three answers before a message is filed: what the sender wants, how soon it matters, and which team owns it. One call scores all three heads on the same text, so the router does not run the model three times.

model.classify_text(
    "From: compliance@group.example\nSubject: Protocol update — action required today\n\nPlease confirm the new retention rule is applied before Friday's audit.",
    {
        "intent": ["fyi", "request", "approval", "complaint", "newsletter", "security_alert"],
        "urgency": ["low", "normal", "high", "critical"],
        "route": ["support", "billing", "legal", "security", "finance", "archive"],
    },
)

Potential output:

{"intent": "request", "urgency": "high", "route": "legal"}

Ticket routing

Employees describe a problem, not a department. Payroll, benefits, IT access, and facilities share the same portal. The queue label is the assignment, so the ticket opens in the right team instead of bouncing through a dispatcher.

model.classify_text(
    "[subject] 401k deduction missing from this paystub\n[body] Last month's contribution posted. This month the line is gone and HR told me to open a ticket.",
    {"queue": [
        "payroll", "benefits", "it_access", "facilities",
        "expense_reimbursement", "manager_approval",
    ]},
)

Potential output:

{"queue": "benefits"}

Handoff to a person

Most turns should stay automated. A repeated complaint, an explicit request for a human, or a case the bot cannot close should leave the flow. This is the yes/no gate in front of an agent queue.

model.classify_text(
    "This is the third time I have explained the same missing refund. Stop the bot and get me a person.",
    {"handoff": ["yes", "no"]},
)

Potential output:

{"handoff": "yes"}

Did the agent finish?

A trace can look busy and still be incomplete: a draft saved, a button disabled, a required field empty. Supervisors and eval harnesses need a finish decision from the goal plus the last state, not from whether the model stopped talking.

model.classify_text(
    "Goal: email the Q4 summary to every partner.\nLast action: draft saved in the hub.\nSend button is still disabled because two partners have no address.",
    {"finished": ["yes", "no"]},
)

Potential output:

{"finished": "no"}

Moderation

User content and model output both need a policy decision before they are shown or acted on. The labels are the policy, from allow through personal data, harassment, scam, and spam, so a filter can block, redact, or escalate.

model.classify_text(
    "Post the customer's home address in the public thread so everyone can see where the package actually went.",
    {"policy": ["allow", "personal_data", "harassment", "scam", "violence", "spam"]},
)

Potential output:

{"policy": "personal_data"}

Incident severity

Pages and deploys produce more notes than pages. Severity is what decides whether this wakes someone up. Staging-only tag drift is not a production checkout failure, and the label should say so.

model.classify_text(
    "The deploy left resource tags inconsistent across staging. Production checkout is unaffected. No customer reports yet.",
    {"severity": ["info", "low", "medium", "high", "critical"]},
)

Potential output:

{"severity": "low"}

Urgency score

Some queues want a rank, not a bucket. Pass "0" through "5" as ordinary strings. A payroll cutoff before 5pm and a typo in a wiki page should not receive the same score, and the label is what the SLA system reads.

model.classify_text(
    "Payroll file has to be corrected before the 5pm cutoff or the whole company is paid late.",
    {"urgency": ["0", "1", "2", "3", "4", "5"]},
)

Potential output:

{"urgency": "5"}

Spam or not

The first filter on an inbox or a comment stream. Phishing and mailbox-full lures should never reach the intent router. A two-label decision keeps that check cheap enough to run on every message.

model.classify_text(
    "Your mailbox is almost full. Click here in the next hour or we will delete every message.",
    {"label": ["spam", "ham"]},
)

Potential output:

{"label": "spam"}

Several decisions at once

Real requests carry more than one fact. A guest can need a room move, a billing release, and a maintenance ticket in the same call. Intent, priority, a human gate, and multi-label topics are scored together, which is how a property system opens the right work orders without a chain of prompts.

model.classify_text(
    "Guest in room 1408 says the AC has been out since yesterday and they want to move tonight or leave. They also asked for the incidentals hold to be released.",
    {
        "intent": ["maintenance", "room_change", "checkout", "billing", "complaint", "amenity_request"],
        "priority": ["low", "normal", "high", "urgent"],
        "needs_human": ["yes", "no"],
        "topics": {
            "labels": ["hvac", "billing", "housekeeping", "noise", "safety"],
            "multi_label": True,
            "cls_threshold": 0.4,
        },
    },
)

Potential output:

{
  "intent": "room_change",
  "priority": "high",
  "needs_human": "yes",
  "topics": ["hvac", "billing"]
}

Question over a passage

The text is the source. The question is the task. Yes or no is the whole answer: no chain of thought, no extracted sentence, just the decision a checker or a form needs.

model.classify_text(
    "The treaty was signed in Paris in 1992. It entered into force the following year, after the last signatory ratified it.",
    {"answer": {
        "labels": ["yes", "no"],
        "prompt": "Did the treaty enter into force in 1992?",
    }},
)

Potential output:

{"answer": "no"}

Book

A catalog, a slush pile, or a library inbox needs a genre before anyone writes a blurb. The passage is enough. The label set is the shelf list.

model.classify_text(
    "She closed the ledger, blew out the lamp, and listened for the stair. The house had been empty since the winter the river took the bridge.",
    {"genre": ["mystery", "romance", "history", "science_fiction", "literary_fiction", "cookbook"]},
)

Potential output:

{"genre": "literary_fiction"}

Labels with a description

When the name of a label is not enough, pass a short description with it. The description is part of the decision, which is how a private taxonomy stays precise without a bigger model.

model.classify_text(
    "Please reset the card PIN. The new one never arrived and the old one is locked after three tries.",
    {"intent": {
        "labels": {
            "card_pin_change": "The customer wants a new PIN or the current PIN replaced",
            "card_lost": "The physical card is missing",
            "balance_inquiry": "The customer wants the current balance",
        },
    }},
)

Potential output:

{"intent": "card_pin_change"}

Ordinal score

Some products want a rank, not a class. Pass the scale as ordinary strings, from "0" to "10". A review, a rubric, or a satisfaction form can read the label directly.

model.classify_text(
    "I finished it in two nights. The ending is earned, the middle drags, and I would still hand it to a friend.",
    {"rating": ["0", "1", "2", "3", "4", "5", "6", "7", "8", "9", "10"]},
)

Potential output:

{"rating": "7"}

Details

• What it is: a multilingual specialist classifier for operational decisions, including questions over a passage, books, described labels, and ordinal scores
• What it is not: a general-purpose model. No reasoning, no explanations, no open-ended answers.
• Encoder: mDeBERTa-v3-base
• Architecture: boundary
• Base checkpoint: fastino/gliner2.5-multi-v1
• Runs on: CPU or GPU, through gliner2
• License: Apache 2.0

Citation

@misc{zaratiana2025gliner2efficientmultitaskinformation,
      title={GLiNER2: An Efficient Multi-Task Information Extraction System with Schema-Driven Interface},
      author={Urchade Zaratiana and Gil Pasternak and Oliver Boyd and George Hurn-Maloney and Ash Lewis},
      year={2025},
      eprint={2507.18546},
      archivePrefix={arXiv},
      primaryClass={cs.CL},
      url={https://arxiv.org/abs/2507.18546},
}