@inproceedings{zhang-etal-2026-robust-explanations,
    title = "Robust Explanations for User Trust in Enterprise {NLP} Systems",
    author = "Zhang, Guilin  and
      Zhao, Kai  and
      Friedman, Jeffrey  and
      Chu, Xu  and
      Anoun, Amine",
    editor = "Li, Yunyao  and
      Rehm, Georg  and
      Tu, Mei",
    booktitle = "Proceedings of the 64th Annual Meeting of the {A}ssociation for {C}omputational {L}inguistics ({ACL} 2026)",
    month = jul,
    year = "2026",
    address = "San Diego, California, USA",
    publisher = "Association for Computational Linguistics",
    url = "https://preview.aclanthology.org/ingest-acl/2026.acl-industry.81/",
    pages = "1150--1158",
    ISBN = "979-8-89176-394-4",
    abstract = "Robust explanations are increasingly required for user trust in enterprise NLP, yet pre-deployment validation is difficult in the common case of black-box deployment (API-only access) where representation-based explainers are infeasible and existing studies provide limited guidance on whether explanations remain stable under real user noise, especially when organizations migrate from encoder classifiers to decoder LLMs. To close this gap, we propose a unified black-box robustness evaluation framework for token-level explanations based on leave-one-out occlusion, and operationalize explanation robustness with top-token flip rate under realistic perturbations (swap, deletion, shuffling, and back-translation) at multiple severity levels. Using this protocol, we conduct a systematic cross-architecture comparison across three benchmark datasets and six models spanning encoder and decoder families (BERT, RoBERTa, Qwen 7B/14B, Llama 8B/70B; 64,800 cases). We find that decoder LLMs produce substantially more stable explanations than encoder baselines (73{\%} lower flip rates on average), and that stability improves with model scale (44{\%} gain from 7B to 70B). Finally, we relate robustness improvements to inference cost, yielding a practical cost{--}robustness tradeoff curve that supports model and explanation selection prior to deployment in compliance-sensitive applications."
}