Skip to content

Create an account and get up to 25% off.

Order

Pathway Human Homo sapiens

Semaphorin interactions

R-HSA-373755 in Reactome release 97: under Axon guidance, with 64 genes placed in it by the mapping files and 5 child pathways in the hierarchy.

The same number in the other species

Reactome writes the mouse and rat events it infers from a human pathway under the human number with the species token. A door opens only where that species' own list in this release holds the id: R-MMU-373755 (mouse), R-RNO-373755 (rat). Whether the event was inferred from this one is what the record says.

01The record

Reactome's own record of this pathway

What this tells you

The pathway list, the hierarchy and the genes on this page are read from the files Reactome publishes for Reactome release 97, built into this site on 2026-09-09: the pathway list, the hierarchy relationship file and the two gene mapping files. The record card is the one live read, Reactome's own record of this pathway.

Reactome's download page describes the mapping files: Mapping files link the source database identifier to the lowest level pathway diagram or subset of the pathway, all levels of the pathway hierarchy or database identifier to all reactions. [R13] The gene list here is the all-levels mapping of NCBI Gene ids, filled from the all-levels mapping of Ensembl ids where the NCBI file has no row for a gene; each row names which file it came from by the shape of its source id. Each row carries the evidence codes the file writes for it, as written and unranked, and both where the file writes both; no page of Reactome's documentation the survey read defines the codes, so this page does not expand them. A gene id the identity files do not name is kept as the source's own id with no door rather than turned into a symbol.

On citing what a search finds, Reactome says: It should be remembered that while we strive to contain the most current and accurate data, Reactome should not be used in citations where other primary sources of information are available. [R12] The record card prints the literature Reactome attaches to a curated pathway for that reason. The data are public domain: All data in the Reactome database and files derived from that data are licensed under the Creative Commons Public Domain Dedication (CC0). User may copy, modify, and distribute these data, even for commercial purposes, without asking for permission. Attribution is encouraged but not required. [R10] The pathway illustrations are licensed apart, under CC BY 4.0, and none is shown here.

A gene on this list is one Reactome places in this pathway in this release, and that is all the row says: it does not say the gene is expressed in a tissue or associated with a disease, which are the other two explorers' questions, read from other sources. Reactome's papers of record are [R01] [R02].

  1. [R01] Ragueneau E, Gong C, Sinquin P, Sevilla C, Beavers D, Grentner A, et al. (2026). The Reactome Knowledgebase 2026. Nucleic Acids Research 54:D673-D681. PMID 41251150, doi 10.1093/nar/gkaf1223.
  2. [R02] Milacic M, Beavers D, Conley P, Gong C, Gillespie M, Griss J, et al. (2024). The Reactome Pathway Knowledgebase 2024. Nucleic Acids Research 52:D672-D678. PMID 37941124, doi 10.1093/nar/gkad1025.
  3. [R10] Reactome, reactome.org. License Agreement. https://reactome.org/license, read 2026-09-09.
  4. [R12] Reactome, reactome.org. Citing us. https://reactome.org/cite, read 2026-09-09.
  5. [R13] Reactome, reactome.org. Download. https://reactome.org/download-data, read 2026-09-09.
Reading this pathway's record from Reactome (the pathway record).Still reading. A first read of a pathway can take a while; this page waits up to 35 seconds for it, and its scripts then bring in the panel, or a line saying what did not arrive.

02The genes

Genes Reactome places in this human pathway

The mapping files place 64 genes in this human pathway; showing 1 to 64, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this human pathway, page 1 of 1
GeneARHGAP35AuthorityHGNC:4591Mapping file id2909 NCBI fileEvidenceTAS
GeneARHGEF11AuthorityHGNC:14580Mapping file id9826 NCBI fileEvidenceTAS
GeneARHGEF12AuthorityHGNC:14193Mapping file id23365 NCBI fileEvidenceTAS
GeneCD72AuthorityHGNC:1696Mapping file id971 NCBI fileEvidenceTAS
GeneCDK5AuthorityHGNC:1774Mapping file id1020 NCBI fileEvidenceIEA, TAS
GeneCDK5R1AuthorityHGNC:1775Mapping file id8851 NCBI fileEvidenceIEA, TAS
GeneCFL1AuthorityHGNC:1874Mapping file id1072 NCBI fileEvidenceIEA
GeneCRMP1AuthorityHGNC:2365Mapping file id1400 NCBI fileEvidenceTAS
GeneDPYSL2AuthorityHGNC:3014Mapping file id1808 NCBI fileEvidenceTAS
GeneDPYSL3AuthorityHGNC:3015Mapping file id1809 NCBI fileEvidenceTAS
GeneDPYSL4AuthorityHGNC:3016Mapping file id10570 NCBI fileEvidenceTAS
GeneDPYSL5AuthorityHGNC:20637Mapping file id56896 NCBI fileEvidenceTAS
GeneERBB2AuthorityHGNC:3430Mapping file id2064 NCBI fileEvidenceTAS
GeneFARP2AuthorityHGNC:16460Mapping file id9855 NCBI fileEvidenceIEA, TAS
GeneFESAuthorityHGNC:3657Mapping file id2242 NCBI fileEvidenceIEA, TAS
GeneFYNAuthorityHGNC:4037Mapping file id2534 NCBI fileEvidenceIEA, TAS
GeneGSK3BAuthorityHGNC:4617Mapping file id2932 NCBI fileEvidenceTAS
GeneHSP90AA1AuthorityHGNC:5253Mapping file id3320 NCBI fileEvidenceTAS
GeneHSP90AB1AuthorityHGNC:5258Mapping file id3326 NCBI fileEvidenceTAS
GeneITGA1AuthorityHGNC:6134Mapping file id3672 NCBI fileEvidenceIEA
GeneITGB1AuthorityHGNC:6153Mapping file id3688 NCBI fileEvidenceIEA
GeneLIMK1AuthorityHGNC:6613Mapping file id3984 NCBI fileEvidenceIEA, TAS
GeneLIMK2AuthorityHGNC:6614Mapping file id3985 NCBI fileEvidenceIEA
GeneMETAuthorityHGNC:7029Mapping file id4233 NCBI fileEvidenceTAS
GeneMYH10AuthorityHGNC:7568Mapping file id4628 NCBI fileEvidenceIEA
GeneMYH11AuthorityHGNC:7569Mapping file id4629 NCBI fileEvidenceIEA
GeneMYH14AuthorityHGNC:23212Mapping file id79784 NCBI fileEvidenceIEA
GeneMYH9AuthorityHGNC:7579Mapping file id4627 NCBI fileEvidenceIEA
GeneMYL12BAuthorityHGNC:29827Mapping file id103910 NCBI fileEvidenceIEA
GeneMYL6AuthorityHGNC:7587Mapping file id4637 NCBI fileEvidenceIEA
GeneMYL9AuthorityHGNC:15754Mapping file id10398 NCBI fileEvidenceIEA
GeneNRP1AuthorityHGNC:8004Mapping file id8829 NCBI fileEvidenceIEA, TAS
GenePAK1AuthorityHGNC:8590Mapping file id5058 NCBI fileEvidenceTAS
GenePAK2AuthorityHGNC:8591Mapping file id5062 NCBI fileEvidenceTAS
GenePAK3AuthorityHGNC:8592Mapping file id5063 NCBI fileEvidenceTAS
GenePIP5K1CAuthorityHGNC:8996Mapping file id23396 NCBI fileEvidenceTAS
GenePLXNA1AuthorityHGNC:9099Mapping file id5361 NCBI fileEvidenceIEA, TAS
GenePLXNA2AuthorityHGNC:9100Mapping file id5362 NCBI fileEvidenceIEA, TAS
GenePLXNA3AuthorityHGNC:9101Mapping file id55558 NCBI fileEvidenceIEA, TAS
GenePLXNA4AuthorityHGNC:9102Mapping file id91584 NCBI fileEvidenceIEA, TAS
GenePLXNB1AuthorityHGNC:9103Mapping file id5364 NCBI fileEvidenceTAS
GenePLXNB3AuthorityHGNC:9105Mapping file id5365 NCBI fileEvidenceTAS
GenePLXNC1AuthorityHGNC:9106Mapping file id10154 NCBI fileEvidenceTAS
GenePLXND1AuthorityHGNC:9107Mapping file id23129 NCBI fileEvidenceTAS
GenePTPRCAuthorityHGNC:9666Mapping file id5788 NCBI fileEvidenceTAS
GeneRAC1AuthorityHGNC:9801Mapping file id5879 NCBI fileEvidenceIEA, TAS
GeneRHOAAuthorityHGNC:667Mapping file id387 NCBI fileEvidenceIEA, TAS
GeneRHOBAuthorityHGNC:668Mapping file id388 NCBI fileEvidenceIEA, TAS
GeneRHOCAuthorityHGNC:669Mapping file id389 NCBI fileEvidenceIEA, TAS
GeneRND1AuthorityHGNC:18314Mapping file id27289 NCBI fileEvidenceIEA, TAS
GeneROCK1AuthorityHGNC:10251Mapping file id6093 NCBI fileEvidenceIEA, TAS
GeneROCK2AuthorityHGNC:10252Mapping file id9475 NCBI fileEvidenceIEA, TAS
GeneRRASAuthorityHGNC:10447Mapping file id6237 NCBI fileEvidenceIEA, TAS
GeneSEMA3AAuthorityHGNC:10723Mapping file id10371 NCBI fileEvidenceIEA, TAS
GeneSEMA3EAuthorityHGNC:10727Mapping file id9723 NCBI fileEvidenceTAS
GeneSEMA4AAuthorityHGNC:10729Mapping file id64218 NCBI fileEvidenceTAS
GeneSEMA4DAuthorityHGNC:10732Mapping file id10507 NCBI fileEvidenceTAS
GeneSEMA5AAuthorityHGNC:10736Mapping file id9037 NCBI fileEvidenceTAS
GeneSEMA6AAuthorityHGNC:10738Mapping file id57556 NCBI fileEvidenceIEA
GeneSEMA6DAuthorityHGNC:16770Mapping file id80031 NCBI fileEvidenceTAS
GeneSEMA7AAuthorityHGNC:10741Mapping file id8482 NCBI fileEvidenceIEA, TAS
GeneTLN1AuthorityHGNC:11845Mapping file id7094 NCBI fileEvidenceTAS
GeneTREM2AuthorityHGNC:17761Mapping file id54209 NCBI fileEvidenceTAS
GeneTYROBPAuthorityHGNC:12449Mapping file id7305 NCBI fileEvidenceTAS

Evidence codes on this page: IEA, TAS, as the mapping file writes them; a row carrying two was written twice by the file, once under each. The mapping file id says which file placed the gene: an NCBI Gene id from NCBI2Reactome_All_Levels.txt, an Ensembl gene id from Ensembl2Reactome_All_Levels.txt. The two files can disagree about a code, so a row's codes are the one file's view. Measured by this site's build over this release on 2026-09-09: of the 138,908 human pathway-gene pairs both files place, 207 (0.149 per cent, over 47 genes) carry TAS in the Ensembl file where the NCBI rows carry IEA alone.

  • Reactome mapping files, the human rows for this pathway · Reactome release 97 · read · Reactome downloads"NCBI2Reactome_All_Levels.txt" and "Ensembl2Reactome_All_Levels.txt", Reactome, release 97, https://reactome.org/download-data/ (date of access 2026-09-09). Data CC0; attribution encouraged.

03The hierarchy

Parents and children in this release's hierarchy

Reactome's hierarchy is a graph rather than a tree: a pathway can sit under more than one parent, and the gene counts are each pathway's own placements at every level under it, so a parent's count is not the sum of its children's.

  • Reactome, the human pathway list and hierarchy relationship file · Reactome release 97 · read · Reactome downloads"ReactomePathways.txt" and "ReactomePathwaysRelation.txt", Reactome, release 97, https://reactome.org/download-data/ (date of access 2026-09-09). Data CC0; attribution encouraged.