{"about":{"non_affiliation":"Code with Papers and Syntology are not affiliated with, endorsed by, or sponsored by Papers with Code, Meta, or the pwc-archive mirror.","site":"https://codewithpapers.app","licence":"CC BY-SA 4.0","licence_url":"https://creativecommons.org/licenses/by-sa/4.0/legalcode","attribution":"https://codewithpapers.app/attribution","modified":"archive material modified by Syntology; see the attribution page","syntology":{"site":"https://syntology.ai","developers":"https://syntology.ai/developers","mcp":{"server":"https://syntology.ai/mcp","transport":"streamable-http","server_card":"https://syntology.ai/.well-known/mcp/server-card.json","auth":{"type":"trial token, no account","trial_token":"https://syntology.ai/api/oauth/trial/token","method":"POST","docs":"https://syntology.ai/developers"}},"have":"https://syntology.ai/api/graph/have?x=<method, arXiv id or title> (free, answers coverage only)","paper_base":"https://syntology.ai/paper/","atlas_base":"https://app.syntology.ai/?focus="},"machine_readable":[{"url":"https://codewithpapers.app/llms.txt","what":"the machine catalog: every machine-readable file, counted"},{"url":"https://codewithpapers.app/index/manifest.json","what":"paper-to-code index by arXiv id, with Syntology's counts"},{"url":"https://codewithpapers.app/search/manifest.json","what":"site search index (titles, authors) and its files"},{"url":"https://codewithpapers.app/download","what":"bulk files: Syntology's layer, described there"},{"url":"https://codewithpapers.app/build_manifest.json","what":"the build record: inputs, counts, exclusions, probes"}]},"url":"/paper/directing-the-violence-or-admonishing-it-a","title":"Directing the violence or admonishing it? A survey of contronymy and androcentrism in Google Translate and some recommendations","arxiv_id":null,"date":"2021-08-18","proceeding":null,"authors":["Anonymous"],"abstract":"The recent raft of high-profile gaffes involving neural machine translation technologies has brought to light the unreliability of this evolving technology. A worrisome\nfacet of the ubiquity of this technology is that it largely operates in a use-it-at-yourown-peril mode where the user is often unaware of either the idiosyncratic brittleness of the underlying neural translation model or when it is, that the translations\nbe deemed trustworthy and when they wouldn’t. These revelations have worryingly\ncoincided with other developments such as the emergence of large language models\nthat now produce biased and erroneous results, albeit with human-like fluency, the\nuse of back-translation as a data-augmentation strategy in so termed ’low-resource’\nsettings and the emergence of ’AI-enhanced legal-tech’ as a panacea that promises\n’disruptive democratization’ of access to legal services. In the backdrop of these\nquandaries, we present this cautionary tale where we shed light on the specifics\nof the risks surrounding cavalier deployment of this technology by exploring two\nspecific failings: Androcentrism and Enantiosemy. In this regard, we empirically\ninvestigate the fate of the pronouns and a list of contronyms when subjected to\nback-translation using Google Translate. Through this, we seek to highlight the\nprevalence of ’defaulting-to-the-masculine’ phenomenon in the context of engendered profession-related translations and also empirically demonstrate the scale and\nnature of threats pertaining to contronymous phrases covering both current-affairs\nand legal issues. Based on these observations, we have collected a series of recommendations that constitute the latter half of this paper. All of the code and datasets\ngenerated in this paper have been open-sourced for the community to build on here:\nhttps://github.com/rteehas/GT_study_recommendations.\n","url_abs":"https://openreview.net/forum?id=13LjoyYWcaw","url_pdf":"https://openreview.net/pdf?id=13LjoyYWcaw","source":{"archive":"pwc-archive (Hugging Face), CC BY-SA 4.0","snapshot":"2025-07-28","licence_url":"https://creativecommons.org/licenses/by-sa/4.0/legalcode","row_kind":"abstracts"},"code_links":[{"paper_slug":"directing-the-violence-or-admonishing-it-a","repo_url":"https://github.com/rteehas/gt_study_recommendations","is_official":1,"mentioned_in_paper":1,"mentioned_in_github":0,"framework":"none","reach":null}],"tasks":[{"task_slug":"data-augmentation","task_name":"Data Augmentation"},{"task_slug":"machine-translation","task_name":"Machine Translation"},{"task_slug":"translation","task_name":"Translation"}],"methods":[],"datasets_introduced":[],"methods_introduced":[],"results":[],"syntology":{"syntology_url":null,"atlas_url":null,"mcp":null,"developers":"https://syntology.ai/developers","held":null,"reason":"no_arxiv_id","checked_against":null,"by_repo":[{"repo":"rteehas/gt_study_recommendations","kind":"official","samples":0,"ran":0,"instrument":0,"unverified":0}],"by_repo_is":"one row per repository in the archive's code links, Syntology's graph links or the samples; samples 0 means no sample is linked to this paper, a statement about Syntology's coverage, not about the repository: with harvested_for_other_papers present, Syntology harvested the repository for that many other papers, and without it, Syntology harvested nothing from it; placed_by_identical_code counts samples whose link records no repository, placed here because identical code was harvested from this repository for another paper; ran counts executions on a synthesized input and instrument counts failures of Syntology's instrument, not of the code"},"code_links_note":null,"arxiv_metadata":null,"syntology_extracted_results":null,"record_sha256":"48bd0db0040b9fb62fa0e4b9fea19eeab42b6ec7cbd36bbd44cb7af1f685cb7d","record_changed_at":"2026-09-28","record_changed_at_basis":"first_hashed"}