You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Settings:
Text entered into annotator: invasive mammary carcinoma
Select ontology: National Cancer Institute Thesaurus (NCIT)
Select UMLS semantic type: neoplastic process
Result: no annotations found
I am not understanding why the result is 'No annotations found'. The term 'invasive mammary carcinoma' does exist in the NCIT, with semantic_type 'Neoplastic process'.
Our logic for annotating semantic types looks for a property of the class that contains the semantic type code (T191 in this case). Once found, the value is used to set a custom top-level property of the class called “semanticType”. The value of the “semanticType” property is then used when we process classes for the Annotator repository. Looking at the class you provided, there is no property in the class that references the semantic type code. There is one that states the name of the semantic type, “Neoplastic Process”, but that isn’t sufficient for us to classify this as a class belonging to the T191 semantic type:
Here is a sample of a different class from SNOMEDCT that does set the semantic type property and thus appears in your annotation query (if you remove the NCIT ontology filter):
Per user report:
I have been experimenting with the annotator found here:
https://bioportal.bioontology.org/annotator
Settings:
Text entered into annotator: invasive mammary carcinoma
Select ontology: National Cancer Institute Thesaurus (NCIT)
Select UMLS semantic type: neoplastic process
Result: no annotations found
I am not understanding why the result is 'No annotations found'. The term 'invasive mammary carcinoma' does exist in the NCIT, with semantic_type 'Neoplastic process'.
https://bioportal.bioontology.org/ontologies/NCIT?p=classes&conceptid=http%3A%2F%2Fncicb.nci.nih.gov%2Fxml%2Fowl%2FEVS%2FThesaurus.owl%23C9245
The text was updated successfully, but these errors were encountered: