The Simple Standard for Sharing Ontological Mappings (SSSOM) requires semantic mappings to annotate a justification from the Semantic Mapping Vocabulary (SEMAPV) such as semapv:ManualMappingCuration, semapv:MappingInversion, and semapv:MappingChaining. However, SSSOM did not have a mechanism for tracking which mappings were used during inference workflows like inversion or chaining. This post is about my recent SSSOM enhancement proposal to add a new field derived_from to support this.

Background

Before we get started, it’s worth defining a few terms about mappings to make sure that we stay precise.

Mapping Triple

A mapping triple is a subject, predicate, and object such as mesh:C000089, skos:exactMatch, CHEBI:28646. By semantic web conventions based on the open world assumption (OWA), triples are assumed to be true unless stated otherwise.

flowchart LR
    mesh:C000089[ammeline
mesh:C000089]
CHEBI:28646[ammeline
CHEBI:28646]

mesh:C000089-->|skos:exactMatch|CHEBI:28646

Mapping Quadruple

A mapping quadruple is a subject, predicate, object, and truthiness (a boolean). SSSOM represents the truthiness using the predicate_modifier field, where an empty value means that the mapping is true, and a value of Not means that it is false.

For example, (mesh:C000089, skos:exactMatch, CHEBI:28646, True) makes the example mapping triple from above into a mapping quadruple that explicitly states its truthiness.

flowchart LR
    mesh:C000089[ammeline
mesh:C000089]
CHEBI:28646[ammeline
CHEBI:28646]

mesh:C000089-->|"skos:exactMatch\n(true)"|CHEBI:28646

Conversely, (CHEBI:10057, skos:exactMatch, mesh:C002563, False) is false because CHEBI:10057 refers to 9H-xanthene, a small molecule, and mesh:C002563 refers to xanthan gum, a polysaccharide.

flowchart LR
    mesh:C002563[xanthan gum
mesh:C000089]
CHEBI:10057[9H-xanthene
CHEBI:10057]

mesh:C002563-->|"not skos:exactMatch"|CHEBI:10057

By convention, mapping triples are implicitly considered to refer to the corresponding true mapping quadruple.

Mapping Record

A mapping record is a subject, predicate, object, truthiness, and other metadata about the mapping that appears in the SSSOM Mapping data model. A mapping record best be visualized by reifying the triple (i.e., make into a node) to show how additional metadata is connected.

flowchart LR
    mesh:C000089[ammeline
mesh:C000089]
CHEBI:28646[ammeline
CHEBI:28646]
1181E81AD58C1B94("mesh:C000089
skos:exactMatch
CHEBI:28646
manual curation")
style 1181E81AD58C1B94 fill:#bbf
orcid:0000-0003-4423-4370[Charles Tapley Hoyt
orcid:0000-0003-4423-4370]
style orcid:0000-0003-4423-4370 fill: #bef
wikidata:Q111239110[Biomappings
wikidata:Q111239110]
style wikidata:Q111239110 fill: #feb
1181E81AD58C1B94 -->|has author|orcid:0000-0003-4423-4370
1181E81AD58C1B94-->|source|wikidata:Q111239110
mesh:C000089 -->|subject of|1181E81AD58C1B94
CHEBI:28646 -->|object of|1181E81AD58C1B94

Note that I’m playing a bit fast and loose with the semantics of the predicates relating the mapping record to other components. This is explicitly specified as part of SSSOM, but I don’t think super instructive here, so I’ve used more human-readable labels.

Motivation

I’ve been thinking about the large-scale aggregation and inference over semantic mappings for several years now. My initial work resulted in the implementation of the Semantic Mapping Reasoner and Assembler (SeMRA) and the publication of its companion article Assembly and reasoning over semantic mappings at scale for biomedical data integration.

Initially, SeMRA implemented a custom data model that was similar to SSSOM, but had a more explicit provenance model for which mapping records (e.g., from SSSOM) were used to infer/derive new mapping quadruples. As SeMRA and its applications have matured, I have been able to backport many of its good ideas to SSSOM. This post is specifically about how I’ve proposed a simple, optional, explicit provenance model that allows mapping records in SSSOM derived through inference to reference the set of mapping quadruples that were used during inference, in a new derived_from slot.

Reference the Triple, Quadruple, or Record?

This slot is deliberately under-specified, but there’s a key nuance that the values in this field should point to identifiers for mapping quadruples, not mapping triples nor mapping records for the following reasons:

  1. Mapping triples are insufficient: without the judgment of whether a mapping is true or false, then an algorithm could accidentally conclude from A skos:exactMatch B and B (not) skos:exactMatch C that A skos:exactMatch C. This is why mapping triples are insufficient
  2. Inference happens on the mapping quadruple level, so it matches nicely
  3. Full mapping records are inflexible: the SSSOM data should be flexible so if additional evidence (i.e., records) for a given mapping quadruple are found, then the confidence in the inferred/derived mapping (e.g., chained or inverted) can be adjusted accordingly. This is possible because most chaining and inversion algorithms logically operate on mapping quadruples, and not on records.

This is why in the following diagrams, there are mapping quads represented in pink boxes and mapping records represented by purple boxes.

Note: the local unique identifiers used for mappings in this example are related to the proposal in https://github.com/ts4nfdi/mapping-sameness-identifier (which currently is under review). For now, the SSSOM specification isn’t prescribing how to assign identifiers to mapping quadruples.

Contribution

See the original issue mapping-commons/sssom#537 and pull request mapping-commons/sssom#548. This post is an extension of the documentation I wrote in that PR (https://mapping-commons.github.io/sssom/dev/inference).

I implemented the derived_from field in SSSOM Pydantic in cthoyt/sssom-pydantic#108. Subsequently, while preparing this post, I implemented a mechanism for generating the pretty Mermaid diagrams I’ve used throughout this post in cthoyt/sssom-pydantic#129.

Here’s how this looks in Python:

from curies import Converter, NamableReference, NamedReference
from curies.vocabulary import charlie, manual_mapping_curation, mapping_chaining, exact_match

from sssom_pydantic import SemanticMapping, hash_triple_to_reference

CONVERTER = Converter.from_prefix_map({
    "BTO": "http://purl.obolibrary.org/obo/CHEBI_",
    "CL": "http://purl.obolibrary.org/obo/CL_",
    "mesh": "http://id.nlm.nih.gov/mesh/",
    "wikidata": "http://www.wikidata.org/entity/",
    "orcid": "https://orcid.org/",
    "semapv": "https://w3id.org/semapv/vocab/",
    "skos": "http://www.w3.org/2004/02/skos/core#",

})

E1 = NamedReference.from_curie("BTO:0006078", name="pluripotent stem cell")
E2 = NamedReference.from_curie("CL:0002248", name="pluripotent stem cell")
E3 = NamedReference.from_curie("mesh:D039904", name="Pluripotent Stem Cells")
SOURCE = NamableReference.from_curie("wikidata:Q111239110", name="Biomappings")

m1 = SemanticMapping(
    subject=E1,
    predicate=exact_match,
    object=E2,
    justification=manual_mapping_curation,
    authors=[charlie],
    source=SOURCE,
)
m2 = SemanticMapping(
    subject=E2,
    predicate=exact_match,
    object=E3,
    justification=manual_mapping_curation,
    authors=[charlie],
    source=SOURCE,
)
m3 = SemanticMapping(
    subject=E1,
    predicate=exact_match,
    object=E3,
    justification=mapping_chaining,
    # This is the new part!
    derived_from=[
        hash_triple_to_reference(m1, CONVERTER),
        hash_triple_to_reference(m2, CONVERTER),
    ],
)

Damien Goutte-Gattat also implemented the derived_from in SSSOM Java in gouttegd/sssom-java#19.

Examples

To finish off this post, I’ve included five real-world examples combining manually curated mappings from Biomappings and the ChEBI ontology that show off three types of inference: inversion, chaining, and background knowledge-based mapping.

Inversion

A mapping inversion workflow inverts the mapping predicate then swaps subject and object components. For example, the mapping predicate skos:narrowMatch andskos:broadMatch are inverses and skos:exactMatch is its own inverse. More information about mapping predicates can be found in the SSSOM documentation.

The introduction of the derived_from field allows an inverted mapping record to refer back to the mapping it was derived from.

In the example below, a manually curated mapping between MeSH and ChEBI’s terms for ammeline is inverted.

flowchart LR
    mesh:C000089[ammeline
mesh:C000089]
CHEBI:28646[ammeline
CHEBI:28646]
1181E81AD58C1B94("mesh:C000089
skos:exactMatch
CHEBI:28646
manual curation")
style 1181E81AD58C1B94 fill:#bbf
orcid:0000-0003-4423-4370[Charles Tapley Hoyt
orcid:0000-0003-4423-4370]
style orcid:0000-0003-4423-4370 fill: #bef
wikidata:Q111239110[Biomappings
wikidata:Q111239110]
style wikidata:Q111239110 fill: #feb
36a1f9244ea7641a90987c82f33c25c0c13712ee8f48207b2a0825f8a4e4e26a[["mesh:C000089
skos:exactMatch
CHEBI:28646"]]
style 36a1f9244ea7641a90987c82f33c25c0c13712ee8f48207b2a0825f8a4e4e26a fill: #f9f
54D1553627DC5514("CHEBI:28646
skos:exactMatch
mesh:C000089
inversion")
style 54D1553627DC5514 fill: #bbf
faeefc6d1dd08238a9732de5a3c9dcf99388e62fa8b1caaf9ba28c7eaf6d483a[["CHEBI:28646
skos:exactMatch
mesh:C000089"]]
style faeefc6d1dd08238a9732de5a3c9dcf99388e62fa8b1caaf9ba28c7eaf6d483a fill: #f9f
1181E81AD58C1B94 -->|has author|orcid:0000-0003-4423-4370
1181E81AD58C1B94-->|source|wikidata:Q111239110
mesh:C000089 -->|subject of|1181E81AD58C1B94
CHEBI:28646 -->|object of|1181E81AD58C1B94
36a1f9244ea7641a90987c82f33c25c0c13712ee8f48207b2a0825f8a4e4e26a -->|has evidence|1181E81AD58C1B94
CHEBI:28646 -->|subject of|54D1553627DC5514
mesh:C000089 -->|object of|54D1553627DC5514
faeefc6d1dd08238a9732de5a3c9dcf99388e62fa8b1caaf9ba28c7eaf6d483a -->|has evidence|54D1553627DC5514
54D1553627DC5514 -->|derived from|36a1f9244ea7641a90987c82f33c25c0c13712ee8f48207b2a0825f8a4e4e26a
Source SSSOM TSV
subject_id subject_label predicate_id object_id object_label mapping_justification author_id mapping_source derived_from
mesh:C000089 ammeline skos:exactMatch chebi:28646 ammeline semapv:ManualMappingCuration orcid:0000-0003-4423-4370 wikidata:Q111239110
chebi:28646 ammeline skos:exactMatch mesh:C000089 ammeline semapv:MappingInversion mapping:36a1f9244ea7641a90987c82f33c25c0c13712ee8f48207b2a0825f8a4e4e26a

Chaining

A mapping chaining workflow applies SSSOM chaining rules to combine one or more mappings who share subjects/objects. The resulting mappings should be tagged with semapv:MappingChaining as a justification.

Depending on the implementation, directionality is important, so inferring inverted mappings before chaining is important.

flowchart LR
    BTO:0006078[pluripotent stem cell
BTO:0006078]
CL:0002248[pluripotent stem cell
CL:0002248]
EEB83E3B60649C0E("BTO:0006078
skos:exactMatch
CL:0002248
manual curation")
style EEB83E3B60649C0E fill: #bbf
orcid:0000-0003-4423-4370[Charles Tapley Hoyt
orcid:0000-0003-4423-4370]
style orcid:0000-0003-4423-4370 fill: #bef
wikidata:Q111239110[Biomappings
wikidata:Q111239110]
style wikidata:Q111239110 fill:#feb
8a12a396b85642cccfc799fb24320c51a4aabf3294780cb31116d45f773a2572[["BTO:0006078
skos:exactMatch
CL:0002248"]]
style 8a12a396b85642cccfc799fb24320c51a4aabf3294780cb31116d45f773a2572 fill: #f9f
mesh:D039904[pluripotent stem cells
mesh:D039904]
CD2204936C2DDC93("CL:0002248
skos:exactMatch
mesh:D039904
manual curation")
style CD2204936C2DDC93 fill: #bbf
988ce14e26fdbf24aeb27b4d8b5ad4bcc25b5cdb46be4e674bfa88a2abe12264[["CL:0002248
skos:exactMatch
mesh:D039904"]]
style 988ce14e26fdbf24aeb27b4d8b5ad4bcc25b5cdb46be4e674bfa88a2abe12264 fill: #f9f
AC5F57BF466F5641("BTO:0006078
skos:exactMatch
mesh:D039904
chaining")
style AC5F57BF466F5641 fill: #bbf
0d2804dff03667d435d38f61e97cd8435382ad45104c6be460f9aa318e0a4622[["BTO:0006078
skos:exactMatch
mesh:D039904"]]
style 0d2804dff03667d435d38f61e97cd8435382ad45104c6be460f9aa318e0a4622 fill: #f9f
EEB83E3B60649C0E -->|has author|orcid:0000-0003-4423-4370
EEB83E3B60649C0E-->|source|wikidata:Q111239110
BTO:0006078 -->|subject of|EEB83E3B60649C0E
CL:0002248 -->|object of|EEB83E3B60649C0E
8a12a396b85642cccfc799fb24320c51a4aabf3294780cb31116d45f773a2572 -->|has evidence|EEB83E3B60649C0E
CD2204936C2DDC93 -->|has author|orcid:0000-0003-4423-4370
CD2204936C2DDC93 -->|source|wikidata:Q111239110
CL:0002248 -->|subject of|CD2204936C2DDC93
mesh:D039904 -->|object of|CD2204936C2DDC93
988ce14e26fdbf24aeb27b4d8b5ad4bcc25b5cdb46be4e674bfa88a2abe12264 -->|has evidence|CD2204936C2DDC93
BTO:0006078 -->|subject of|AC5F57BF466F5641
mesh:D039904 -->|object of|AC5F57BF466F5641
0d2804dff03667d435d38f61e97cd8435382ad45104c6be460f9aa318e0a4622-->|has evidence|AC5F57BF466F5641
AC5F57BF466F5641 -->|derived from|8a12a396b85642cccfc799fb24320c51a4aabf3294780cb31116d45f773a2572
AC5F57BF466F5641 -->|derived from|988ce14e26fdbf24aeb27b4d8b5ad4bcc25b5cdb46be4e674bfa88a2abe12264
Source SSSOM TSV
subject_id subject_label predicate_id object_id object_label mapping_justification author_id mapping_source derived_from
BTO:0006078 pluripotent stem cell skos:exactMatch CL:0002248 pluripotent stem cell semapv:ManualMappingCuration orcid:0000-0003-4423-4370 wikidata:Q111239110
CL:0002248 pluripotent stem cell skos:exactMatch mesh:D039904 Pluripotent Stem Cells semapv:ManualMappingCuration orcid:0000-0003-4423-4370 wikidata:Q111239110
BTO:0006078 pluripotent stem cell skos:exactMatch mesh:D039904 Pluripotent Stem Cells semapv:MappingChaining mapping:8a12a396b85642cccfc799fb24320c51a4aabf3294780cb31116d45f773a2572|mapping:988ce14e26fdbf24aeb27b4d8b5ad4bcc25b5cdb46be4e674bfa88a2abe12264

Chaining with Negatives

When I wrote the initial SSSOM chaining rules, I did not include any examples on how negative modifiers interact with the rules. This example is a prospective look on how negative mappings and positive mappings could interact. I will be making some improvements to the SSSOM docs with additional concrete rules soon.

flowchart LR
    CHEBI:10057[9H-xanthene
CHEBI:10057]
mesh:C002563[xanthan gum
mesh:C002563]
462D9D4128330C63("CHEBI:10057
not skos:exactMatch
mesh:C002563
manual curation")
style 462D9D4128330C63 fill: #bbf
orcid:0000-0003-4423-4370[Charles Tapley Hoyt
orcid:0000-0003-4423-4370]
style orcid:0000-0003-4423-4370 fill: #bef
wikidata:Q111239110[Biomappings
wikidata:Q111239110]
style wikidata:Q111239110 fill:#feb
58f24ccfaf71431276da873c9e7b77ea61a2425e4e8b283b943542290deb292bN[["CHEBI:10057
not skos:exactMatch
mesh:C002563"]]
style 58f24ccfaf71431276da873c9e7b77ea61a2425e4e8b283b943542290deb292bN fill: #f9f
cas:92-83-1[Xanthene
cas:92-83-1]
190EA9377428B4CB("cas:92-83-1
skos:exactMatch
CHEBI:10057
manual curation")
style 190EA9377428B4CB fill: #bbf
bb1162fb2afb1c519c0aa8be98c352061720af220e2d052c571a1fecabff9800[["cas:92-83-1
skos:exactMatch
CHEBI:10057"]]
style bb1162fb2afb1c519c0aa8be98c352061720af220e2d052c571a1fecabff9800 fill: #f9f
25AC613A93F7EF14("cas:92-83-1
not skos:exactMatch
mesh:C002563
chaining")
style 25AC613A93F7EF14 fill: #bbf
84238c3cc875f0939ee4a8cf76bf33f216784434756833e3ba8d1b1183c372f5N[["cas:92-83-1
not skos:exactMatch
mesh:C002563"]]
style 84238c3cc875f0939ee4a8cf76bf33f216784434756833e3ba8d1b1183c372f5N fill: #f9f
462D9D4128330C63 -->|has author|orcid:0000-0003-4423-4370
462D9D4128330C63 -->|source|wikidata:Q111239110
CHEBI:10057 -->|subject of|462D9D4128330C63
mesh:C002563 -->|object of|462D9D4128330C63
58f24ccfaf71431276da873c9e7b77ea61a2425e4e8b283b943542290deb292bN -->|has evidence|462D9D4128330C63
190EA9377428B4CB -->|has author|orcid:0000-0003-4423-4370
190EA9377428B4CB -->|source|wikidata:Q111239110
cas:92-83-1 -->|subject of|190EA9377428B4CB
CHEBI:10057 -->|object of|190EA9377428B4CB
bb1162fb2afb1c519c0aa8be98c352061720af220e2d052c571a1fecabff9800 -->|has evidence|190EA9377428B4CB
cas:92-83-1 -->|subject of|25AC613A93F7EF14
mesh:C002563 -->|object of|25AC613A93F7EF14
84238c3cc875f0939ee4a8cf76bf33f216784434756833e3ba8d1b1183c372f5N -->|has evidence|25AC613A93F7EF14
25AC613A93F7EF14 -->|derived from|58f24ccfaf71431276da873c9e7b77ea61a2425e4e8b283b943542290deb292bN
25AC613A93F7EF14 -->|derived from|bb1162fb2afb1c519c0aa8be98c352061720af220e2d052c571a1fecabff9800
Source SSSOM TSV
subject_id subject_label predicate_id predicate_modifier object_id object_label mapping_justification author_id mapping_source derived_from
chebi:10057 9H-xanthene skos:exactMatch Not mesh:C002563 xanthan gum semapv:ManualMappingCuration orcid:0000-0003-4423-4370 wikidata:Q111239110
cas:92-83-1 Xanthene skos:exactMatch chebi:10057 9H-xanthene semapv:ManualMappingCuration orcid:0000-0003-4423-4370 wikidata:Q111239110
cas:92-83-1 Xanthene skos:exactMatch Not mesh:C002563 xanthan gum semapv:MappingChaining mapping:58f24ccfaf71431276da873c9e7b77ea61a2425e4e8b283b943542290deb292b~|mapping:bb1162fb2afb1c519c0aa8be98c352061720af220e2d052c571a1fecabff9800

Background Knowledge

Inference based on background knowledge was one of the key contributions of SeMRA. For example, it’s known that mappings in ChEBI to CAS are exact matches, but by curation convention, they’re annotated with the less precise oboInOwl:hasDbXref. Workflows that incorporate this knowledge should be tagged with semapv:BackgroundKnowledgeBasedMatching as a mapping justification.

In this example, I show how a poorly specified mapping from ChEBI is upgraded to an exact match.

flowchart LR
    CHEBI:10057[9H-xanthene
CHEBI:10057]
cas:92-83-1[Xanthene
cas:92-83-1]
964DD2FDA95501A2("CHEBI:10057
oboInOwl:hasDbXref
cas:92-83-1
unspecified")
style 964DD2FDA95501A2 fill: #bbf
obo:chebi[ChEBI Ontology
obo:chebi]
style obo:chebi fill: #feb
887c2cc0c006b49df5fa0bc281e23bd3722880d5096e27218082bd6edf96f59e[["CHEBI:10057
oboInOwl:hasDbXref
cas:92-83-1"]]
style 887c2cc0c006b49df5fa0bc281e23bd3722880d5096e27218082bd6edf96f59e fill: #f9f
B5CF0F3AB755AC6D("CHEBI:10057
skos:exactMatch
cas:92-83-1
background know.")
style B5CF0F3AB755AC6D fill: #bbf
e61f33dbb925f2282823afdad56c24feee9875953ea2de9124a50e47bd63418a[["CHEBI:10057
skos:exactMatch
cas:92-83-1"]]
style e61f33dbb925f2282823afdad56c24feee9875953ea2de9124a50e47bd63418a fill: #f9f
964DD2FDA95501A2 -->|source|obo:chebi
CHEBI:10057 -->|subject of|964DD2FDA95501A2
cas:92-83-1 -->|object of|964DD2FDA95501A2
887c2cc0c006b49df5fa0bc281e23bd3722880d5096e27218082bd6edf96f59e -->|has evidence|964DD2FDA95501A2
CHEBI:10057 -->|subject of|B5CF0F3AB755AC6D
cas:92-83-1 -->|object of|B5CF0F3AB755AC6D
e61f33dbb925f2282823afdad56c24feee9875953ea2de9124a50e47bd63418a -->|has evidence|B5CF0F3AB755AC6D
B5CF0F3AB755AC6D -->|derived from|887c2cc0c006b49df5fa0bc281e23bd3722880d5096e27218082bd6edf96f59e
Source SSSOM TSV
subject_id subject_label predicate_id predicate_label object_id object_label mapping_justification mapping_source derived_from
chebi:10057 9H-xanthene oboInOwl:hasDbXref has database cross-reference cas:92-83-1 Xanthene semapv:UnspecifiedMatching obo:chebi
chebi:10057 9H-xanthene skos:exactMatch cas:92-83-1 Xanthene semapv:BackgroundKnowledgeBasedMatching mapping:887c2cc0c006b49df5fa0bc281e23bd3722880d5096e27218082bd6edf96f59e

End-to-End Inference

This end-to-end example demonstrates the cumulation of inversion, chaining, and background-based workflows. While it only starts with two mappings, it shows how the successive application of these workflows can give full transparency and auditability in the process of inference.

In real-world scenarios, I would want to use the mesh-cas exact match to automatically integrate data, such as in the construction of a knowledge graph. In case this mapping is adjacent to a node important for a prediction, I would want to be able to fully audit how that node was constructed via this mapping diagram.

flowchart LR
    CHEBI:133530[tyramine sulfate
CHEBI:133530]
cas:30223-92-8[Tyramine sulfate
cas:30223-92-8]
983062C7B8D6517E("CHEBI:133530
oboInOwl:hasDbXref
cas:30223-92-8
unspecified")
style 983062C7B8D6517E fill: #bbf
obo:chebi[ChEBI Ontology
obo:chebi]
style obo:chebi fill:#feb
0b8eb968c306d65e1715a7b0961f6a4d99b5b19081edb67cee701fd887af1290[["CHEBI:133530
oboInOwl:hasDbXref
cas:30223-92-8"]]
style 0b8eb968c306d65e1715a7b0961f6a4d99b5b19081edb67cee701fd887af1290 fill: #f9f
21056C0956788E11("CHEBI:133530
skos:exactMatch
cas:30223-92-8
background know.")
style 21056C0956788E11 fill: #bbf
a0022401f47964288ecc1ab706d79b4d4abc10edf33d0a71953834a0b0b3c24c[["CHEBI:133530
skos:exactMatch
cas:30223-92-8"]]
style a0022401f47964288ecc1ab706d79b4d4abc10edf33d0a71953834a0b0b3c24c fill: #f9f
mesh:C027957[tyramine O-sulfate
mesh:C027957]
244808D78AFCBDC1("CHEBI:133530
skos:exactMatch
mesh:C027957
manual curation")
style 244808D78AFCBDC1 fill: #bbf
orcid:0000-0003-4423-4370[Charles Tapley Hoyt
orcid:0000-0003-4423-4370]
style orcid:0000-0003-4423-4370 fill: #bef
wikidata:Q111239110[Biomappings
wikidata:Q111239110]
style wikidata:Q111239110 fill: #feb
b8d737b89a421bd6ca058314564c9ed507cbfe3ec4a2e82979fefdfe708019ea[["CHEBI:133530
skos:exactMatch
mesh:C027957"]]
style b8d737b89a421bd6ca058314564c9ed507cbfe3ec4a2e82979fefdfe708019ea fill: #f9f
474146D6A6AFF3C7("mesh:C027957
skos:exactMatch
CHEBI:133530
inversion")
style 474146D6A6AFF3C7 fill: #bbf
1036c55358639c5db78ada181ac38d8eda337e83efe1db901716d101777f8474[["mesh:C027957
skos:exactMatch
CHEBI:133530"]]
style 1036c55358639c5db78ada181ac38d8eda337e83efe1db901716d101777f8474 fill: #f9f
AED810A43159DA66("mesh:C027957
skos:exactMatch
cas:30223-92-8
chaining")
style AED810A43159DA66 fill: #bbf
b5cd9f2dfa98540a3485a473bed0870720d7de23b87847ba508b8c85961e3b7d[["mesh:C027957
skos:exactMatch
cas:30223-92-8"]]
style b5cd9f2dfa98540a3485a473bed0870720d7de23b87847ba508b8c85961e3b7d fill: #f9f
983062C7B8D6517E -->|source|obo:chebi
CHEBI:133530 -->|subject of|983062C7B8D6517E
cas:30223-92-8 -->|object of|983062C7B8D6517E
0b8eb968c306d65e1715a7b0961f6a4d99b5b19081edb67cee701fd887af1290 -->|has evidence|983062C7B8D6517E
CHEBI:133530 -->|subject of|21056C0956788E11
cas:30223-92-8 -->|object of|21056C0956788E11
a0022401f47964288ecc1ab706d79b4d4abc10edf33d0a71953834a0b0b3c24c -->|has evidence|21056C0956788E11
244808D78AFCBDC1 -->|has author|orcid:0000-0003-4423-4370
244808D78AFCBDC1 -->|source|wikidata:Q111239110
CHEBI:133530 -->|subject of|244808D78AFCBDC1
mesh:C027957 -->|object of|244808D78AFCBDC1
b8d737b89a421bd6ca058314564c9ed507cbfe3ec4a2e82979fefdfe708019ea -->|has evidence|244808D78AFCBDC1
mesh:C027957 -->|subject of|474146D6A6AFF3C7
CHEBI:133530 -->|object of|474146D6A6AFF3C7
1036c55358639c5db78ada181ac38d8eda337e83efe1db901716d101777f8474-->|has evidence|474146D6A6AFF3C7
mesh:C027957-->|subject of|AED810A43159DA66
cas:30223-92-8 -->|object of|AED810A43159DA66
b5cd9f2dfa98540a3485a473bed0870720d7de23b87847ba508b8c85961e3b7d -->|has evidence|AED810A43159DA66
21056C0956788E11-->|derived from|0b8eb968c306d65e1715a7b0961f6a4d99b5b19081edb67cee701fd887af1290
474146D6A6AFF3C7 -->|derived from|b8d737b89a421bd6ca058314564c9ed507cbfe3ec4a2e82979fefdfe708019ea
AED810A43159DA66 -->|derived from|a0022401f47964288ecc1ab706d79b4d4abc10edf33d0a71953834a0b0b3c24c
AED810A43159DA66 -->|derived from|1036c55358639c5db78ada181ac38d8eda337e83efe1db901716d101777f8474
Source SSSOM TSV
subject_id subject_label predicate_id predicate_label object_id object_label mapping_justification mapping_source derived_from author_id
chebi:133530 tyramine sulfate oboInOwl:hasDbXref has database cross-reference cas:30223-92-8 Tyramine sulfate semapv:UnspecifiedMatching obo:chebi
chebi:133530 tyramine sulfate skos:exactMatch cas:30223-92-8 Tyramine sulfate semapv:BackgroundKnowledgeBasedMatching mapping:0b8eb968c306d65e1715a7b0961f6a4d99b5b19081edb67cee701fd887af1290
chebi:133530 tyramine sulfate skos:exactMatch mesh:C027957 tyramine O-sulfate semapv:ManualMappingCuration wikidata:Q111239110 orcid:0000-0003-4423-4370
mesh:C027957 tyramine O-sulfate skos:exactMatch chebi:133530 tyramine sulfate semapv:MappingInversion mapping:b8d737b89a421bd6ca058314564c9ed507cbfe3ec4a2e82979fefdfe708019ea
mesh:C027957 tyramine O-sulfate skos:exactMatch cas:30223-92-8 Tyramine sulfate semapv:MappingChaining mapping:a0022401f47964288ecc1ab706d79b4d4abc10edf33d0a71953834a0b0b3c24c|mapping:1036c55358639c5db78ada181ac38d8eda337e83efe1db901716d101777f8474