# Weird characters in compound synonym

**URL:** https://community.opentargets.org/t/weird-characters-in-compound-synonym/2046
**Category:** Community Feedback
**Created:** [29 June 2026 17:46 UTC](https://community.opentargets.org/t/weird-characters-in-compound-synonym/2046 "2026-06-29T17:46:08Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![irene](https://dub1.discourse-cdn.com/flex017/user_avatar/community.opentargets.org/irene/32/50_2.png) [@irene](https://community.opentargets.org/u/irene)
#### Post date: [30 June 2026 08:48 UTC](https://community.opentargets.org/t/weird-characters-in-compound-synonym/2046/2 "2026-06-30T08:48:42Z")

</div>

Hi @Tiejun_Cheng and welcome to our community!

Thank you for the detailed bug report. After your message, we’ve identified that the root cause is in the _LLM extraction_ input data. Some responses from the OpenAI Batch API returns corrupted JSON escape sequences (\u0000 instead of \u00 for accented characters like é, ö, ® as you have noted), which json.loads() then interprets as embedded null bytes.

This affects:

- 171 rows in investigated\_drugs.synonyms that we use for **`drug_molecule`**
- 6 rows in diseases.diseaseFromSource in **`clinical_report`**
- … and \*\*`evidence_clinical_precedence`\*\*and **`clinical_target`** because they propagate the malformed disease names we see in the above datasets

We will prepare a fix for our next release that patches the intended characters from the corrupted escape sequences (e.g., `\x00e9` → `é`). In the meantime, we hope you can omit or work around these affected rows on your end. We apologise for the inconvenience. Please let us know if you find any other issues.

Best,  
Irene

---

_[View the full topic](https://community.opentargets.org/t/weird-characters-in-compound-synonym/2046)._