PMC:7258756 / 3792-3980 JSONTXT

{"project":"LitCovid-PubTator","denotations":[{"id":"87","span":{"begin":24,"end":34},"obj":"Species"},{"id":"88","span":{"begin":98,"end":108},"obj":"Species"}],"attributes":[{"id":"A87","pred":"tao:has_database_id","subj":"87","obj":"Tax:2697049"},{"id":"A88","pred":"tao:has_database_id","subj":"88","obj":"Tax:2697049"}],"namespaces":[{"prefix":"Tax","uri":"https://www.ncbi.nlm.nih.gov/taxonomy/"},{"prefix":"MESH","uri":"https://id.nlm.nih.gov/mesh/"},{"prefix":"Gene","uri":"https://www.ncbi.nlm.nih.gov/gene/"},{"prefix":"CVCL","uri":"https://web.expasy.org/cellosaurus/CVCL_"}],"text":"19-nCoV is now named as SARS-CoV-27. Further, based on SimPlot analyses, it was demonstrated that SARS-CoV-2 was more closely related to the BatCoV RaTG13 sequence (~96.3% similarity) thro"}

{"project":"LitCovid-PD-MONDO","denotations":[{"id":"T33","span":{"begin":24,"end":32},"obj":"Disease"},{"id":"T34","span":{"begin":24,"end":28},"obj":"Disease"},{"id":"T35","span":{"begin":98,"end":106},"obj":"Disease"},{"id":"T36","span":{"begin":98,"end":102},"obj":"Disease"}],"attributes":[{"id":"A33","pred":"mondo_id","subj":"T33","obj":"http://purl.obolibrary.org/obo/MONDO_0005091"},{"id":"A34","pred":"mondo_id","subj":"T34","obj":"http://purl.obolibrary.org/obo/MONDO_0005091"},{"id":"A35","pred":"mondo_id","subj":"T35","obj":"http://purl.obolibrary.org/obo/MONDO_0005091"},{"id":"A36","pred":"mondo_id","subj":"T36","obj":"http://purl.obolibrary.org/obo/MONDO_0005091"}],"text":"19-nCoV is now named as SARS-CoV-27. Further, based on SimPlot analyses, it was demonstrated that SARS-CoV-2 was more closely related to the BatCoV RaTG13 sequence (~96.3% similarity) thro"}

{"project":"LitCovid-PD-CLO","denotations":[{"id":"T47","span":{"begin":33,"end":35},"obj":"http://purl.obolibrary.org/obo/CLO_0050509"}],"text":"19-nCoV is now named as SARS-CoV-27. Further, based on SimPlot analyses, it was demonstrated that SARS-CoV-2 was more closely related to the BatCoV RaTG13 sequence (~96.3% similarity) thro"}