Skip to content
OpenTrain AIFor AI Companies

HFEPX · Eval paper review

IndicContextEval: A Benchmark for Evaluating Context Utilisation in Audio Large Language Models Across 8 Indic Languages

Sakshi Joshi, Dhruv Subhash Rathi, Sanskar Singh, Eldho Ittan George +3 more

Published

Jun 17, 2026

Citations

0

Trust level

Low

Usefulness score

0/100 (Low)

Extraction confidence

25% (Low)

Derived from extracted protocol signals and abstract evidence.

Rater population

Not reported

Signals refreshed

Jun 24, 2026

Should you rely on this paper?

This paper is adjacent to HFEPX scope and is best used for background context, not as a primary protocol reference.

Use this as background context only. Do not make protocol decisions from this page alone.

Best use

Background context only

Use if you need

Background context only.

What to verify

Validate the evaluation procedure and quality controls in the full paper before operational use.

Main weakness

This paper looks adjacent to evaluation work, but not like a strong protocol reference.

Human feedback signal
Not explicit
Not explicit in abstract metadata
Evaluation signal
Weak or implicit
Validate from full paper
Usefulness for eval research
0/100
Adjacent candidate

Treat as adjacent context, not a core eval-method reference.

Abstract

AudioLLMs enable speech recognition conditioned on textual prompts such as domain descriptions or entity lists. However, it remains unclear whether these models genuinely utilise such context or rely on parametric knowledge learned during pretraining. Existing benchmarks cannot answer this question because they evaluate transcription under fixed prompting conditions and rarely include explicit contextual inputs. We introduce IndicContextEval, a 56-hour multilingual benchmark of natural speech from 555 speakers across 8 Indian languages and 23 professional domains. We design a 7-level prompting framework that progressively introduces contextual signals, including metadata, natural-language descriptions, entity lists in English and native script, and adversarial prompts with incorrect entities. Evaluating five models reveals substantial differences in context utilisation behaviour, highlighting the need for explicit evaluation of contextual grounding in AudioLLMs.

What we could verify

These are the protocol signals we could actually recover from the available paper metadata. Use them to decide whether this paper is worth deeper reading.

Human Feedback Types

missing

None explicit

No explicit feedback protocol extracted.

"AudioLLMs enable speech recognition conditioned on textual prompts such as domain descriptions or entity lists."

Evaluation Modes

missing

None explicit

Validate eval design from full paper text.

"AudioLLMs enable speech recognition conditioned on textual prompts such as domain descriptions or entity lists."

Quality Controls

missing

Not reported

No explicit QC controls found.

"AudioLLMs enable speech recognition conditioned on textual prompts such as domain descriptions or entity lists."

Benchmarks / Datasets

partial

Indiccontexteval

Useful for quick benchmark comparison.

"We introduce IndicContextEval, a 56-hour multilingual benchmark of natural speech from 555 speakers across 8 Indian languages and 23 professional domains."

Reported Metrics

missing

Not extracted

No metric anchors detected.

"AudioLLMs enable speech recognition conditioned on textual prompts such as domain descriptions or entity lists."

Benchmarks and datasets

Indiccontexteval

Reported metrics

No metric terms were extracted from the available abstract.

Human feedback details
Uses human feedback
No
Feedback types
None
Rater population
Not reported
Expertise required
Multilingual
Evaluation details
Evaluation modes
None
Agentic eval
None
Quality controls
Not reported
Evidence quality
Low
Use this page as
Background context only

Research brief

Metadata summary

AudioLLMs enable speech recognition conditioned on textual prompts such as domain descriptions or entity lists.

Based on abstract + metadata only. Check the source paper before making high-confidence protocol decisions.

Key takeaways

  • AudioLLMs enable speech recognition conditioned on textual prompts such as domain descriptions or entity lists.
  • However, it remains unclear whether these models genuinely utilise such context or rely on parametric knowledge learned during pretraining.
  • Existing benchmarks cannot answer this question because they evaluate transcription under fixed prompting conditions and rarely include explicit contextual inputs.

Researcher actions

  • Compare this paper against nearby papers in the same arXiv category before using it for protocol decisions.
  • Check the full text for explicit evaluation design choices (raters, protocol, and metrics).
  • Use related-paper links to find stronger protocol-specific references.

Caveats

  • Generated from abstract + metadata only; no PDF parsing.
  • Signals below are heuristic and may miss details reported outside the abstract.

Recommended queries

Contribution summary

  • Existing benchmarks cannot answer this question because they evaluate transcription under fixed prompting conditions and rarely include explicit contextual inputs.
  • We introduce IndicContextEval, a 56-hour multilingual benchmark of natural speech from 555 speakers across 8 Indian languages and 23 professional domains.
  • Evaluating five models reveals substantial differences in context utilisation behaviour, highlighting the need for explicit evaluation of contextual grounding in AudioLLMs.

Why it matters for eval

  • Existing benchmarks cannot answer this question because they evaluate transcription under fixed prompting conditions and rarely include explicit contextual inputs.
  • We introduce IndicContextEval, a 56-hour multilingual benchmark of natural speech from 555 speakers across 8 Indian languages and 23 professional domains.

Researcher checklist

  • Human feedback protocol is explicit

    No explicit human feedback protocol detected.

  • Evaluation mode is explicit

    No clear evaluation mode extracted.

  • Quality control reporting appears

    No calibration/adjudication/IAA control explicitly detected.

  • Benchmark or dataset anchors are present

    Detected: Indiccontexteval

  • Metric reporting is present

    No metric terms extracted.