Delivering 3,500+ locale-aware agentic conversations across 15+ languages

Delivered a large-scale multilingual agentic dataset spanning 15+ locales, designed to train and evaluate an AI agent's ability to interpret user requests, select appropriate tools, and execute multi-step workflows across diverse languages and cultural contexts.

3,500+

multi-turn agentic conversations delivered across 15+ locales, spanning tool calls, sequential reasoning chains, and locale-specific instruction following.

15+

locales covered, including English, Korean, Swedish, Dutch, German, French, Italian, Portuguese, Spanish, and Chinese.

10+

quality dimensions evaluated per task, including tool use accuracy, hallucination, system context adherence, datetime reasoning, and naturalness of dialogue.

MethodData generation
DomainTool use
Dataset scale3,500+ conversations
CapabilityData packs
Delivering 3,500+ Locale-Aware Agentic Conversations Across 15+ Language

The challenge

The client needed a high-quality agentic dataset to train and evaluate their AI agent's ability to handle user queries across multiple languages and regions. The core challenges included:

  • Extending reliable tool-calling behavior beyond English: the agent needed to select the correct tools, supply locale-appropriate arguments, and chain calls logically across distinct language environments, each with its own formatting conventions, punctuation rules, and cultural context.
  • Maintaining locale consistency throughout multi-turn interactions:  responses, tool arguments, and conversational references had to remain strictly aligned to the user's locale.
  • Designing system prompts that governed nuanced tool behavior: each task required a detailed, conditional system prompt defining precise tool invocation policies, agent persona, contextual information, and behavioral rules that the agent had to follow throughout the conversation.
  • Capturing realistic, natural interactions at scale: user prompts had to reflect genuine, human-like behavior rather than scripted or tool-aware phrasing, while still implicitly requiring multi-step tool reasoning across every turn.
  • Enforcing structural compliance across thousands of tasks: each conversation had to meet strict turn count requirements, including a minimum number of sequential tool chains and corrected responses.

The approach

Turing deployed a team of trained multilingual evaluators, each assigned to their native locale, operating within a structured task design and review workflow purpose-built for agentic, tool-calling data.

1. Locale-native task design

Each task was assigned to an expert with native-level fluency in the target locale. Experts designed all user prompts and evaluated all agent responses in their assigned language, ensuring that conversational tone, cultural references, and linguistic conventions were authentic rather than translated.

System prompts were written in English but included locale-specific contextual elements, such as locally relevant place names, currencies, entity names, and screen context, to avoid ambiguity without compromising the English-first instruction format.

2. Structured system prompt design

Every system prompt was required to include at least two valid context types, such as current location, device state, user identity, or active application state, alongside at least two explicit tool invocation policies defining how the agent should behave when using specific tools. System prompts also established agent persona, tone, fallback behavior, and conditional logic governing edge cases.

This design ensured that system prompts provided precise, unambiguous instructions that the agent had to follow throughout the conversation, and that evaluators could use as a consistent reference when accepting or rejecting responses.

3. Multi-turn conversation construction

Each conversation was structured as a sequence of 10 to 15 turns, with user prompts crafted to naturally require multiple tool calls, including sequential chains where one tool's output fed the next, and parallel calls where independent requests could be resolved simultaneously.

Tasks were required to include turns demonstrating sequential tool chaining, corrected agent responses, and without tool calls. This structure ensured that every delivered conversation provided dense, high-signal training data for both tool selection and multi-step reasoning.

4. Locale-aware tool argument handling

Tool usage was grounded in the target locale throughout. Argument values, search queries, and conversational references were authored in the user's language, while fallback behavior for edge cases was governed by explicit system prompt instructions, keeping the interaction consistent and locale-appropriate.

5. Three-layer human-in-the-loop quality assurance

Every task passed through a structured three-stage QA process.

  • An automated reviewer ran first, evaluating the task against rubric dimensions including tool use accuracy, hallucination, task completeness, system context adherence, grammar and language quality, naturalness of dialogue, datetime reasoning, tool output integration, and system prompt compliance. Structural validations, such as turn count, rejection counts, cell ordering, and similarity checks were also applied at this stage
  • Human reviewers then validated rubric alignment, locale consistency, and compliance with all system prompt instructions with 100% review coverage across all tasks
  • A calibration layer covered 20–30% of the dataset, where domain leads audited tasks to catch scoring drift, resolve edge cases, and maintain consistent quality standards across locales and evaluator cohorts

Key results

  • More than 3,500 agentic conversations delivered across 15+ locales, each comprising multi-turn interactions with tool calls, sequential reasoning chains, corrected responses, and locale-consistent outputs
  • 10+ rubric dimensions evaluated per task, combining manual expert review with automated LLM-assisted checks across grammar, tool accuracy, hallucination, system adherence, and dialogue naturalness
  • 100% review coverage enforced, with every task passing through both automated pre-submission checks and human reviewer validation before delivery
  • 300+ multilingual evaluators onboarded, spanning software engineering, data science, and ML backgrounds, with experience exceeding five years across technical domains

The outcome

The client received a production-ready multilingual agentic dataset with locale-native conversation design, structured system prompts, and a rigorous dual-layer QA pipeline. The dataset provides high-signal supervision for agents learning to interpret user requests, invoke appropriate tools, and deliver locale-consistent responses in real-world multi-turn workflows.

This foundation supports:

  • Training agents to handle tool-calling across diverse languages without defaulting to English-centric reasoning or formatting conventions
  • Evaluating locale-aware instruction following across a broad range of tool types, invocation sequences, and conversational contexts
  • Calibrating agent behavior under detailed, conditional system prompts that govern persona, tone, fallback logic, and tool use policies
  • Scaling multilingual agentic data production using a validated, rubric-driven workflow with demonstrated quality across 15+ distinct locales

Need locale-aware agentic training data for tool-calling models?

Request a sample of multilingual multi-turn conversations with tool calls, sequential reasoning chains, and rubric-validated outputs across your target locales.

Request Sample

Share

FAQ

What does each conversation include?

Each task is a multi-turn agentic conversation containing a system prompt, locale-native user prompts, agent responses with tool calls, corrected responses where the agent failed, and structured metadata covering locale, task category, tool usage, and turn count.

How was locale consistency enforced?

All user prompts and agent responses were authored and reviewed by native speakers of the target locale. Tool call arguments were required to be in the target language by default, and any cross-locale contamination, including incorrect currency, location, or language defaults was treated as a rubric failure.

How were tool-calling errors handled?

When an agent response contained an incorrect tool selection, missing or hallucinated parameters, wrong argument values, or improper sequencing, evaluators rejected the response, selected the relevant error label, provided a corrected tool call or text response, and added reasoning comments explaining the fix.

What’s the NDA process?

A standard mutual NDA. Turing provides the countersigned agreement within one business day.

How fast can I get a sample?

Within three business days after NDA execution.

Building agents that need to operate reliably across languages and regions?

Request curated agentic conversation data designed for locale-aware tool calling, sequential reasoning, and multi-turn instruction following.

Request Sample

AGI Advance Newsletter

Weekly updates on frontier benchmarks, evals, fine-tuning, and agentic workflows read by top labs and AI practitioners.

Subscribe Now