Skip to content
Order

Pathway Mouse Mus musculus

Read this first

Every mouse pathway in Reactome is electronically inferred from the curated human one; Reactome's own sentence about that stands beside the record below.

Inositol phosphate metabolism

R-MMU-1483249 in Reactome release 97: under Metabolism, with 77 genes placed in it by the mapping files and 8 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-HSA-1483249 (human), R-RNO-1483249 (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.

Every mouse pathway in Reactome is inferred from the curated human one: We use the set of manually curated human reactions to electronically infer reactions in fourteen evolutionarily divergent eukaryotic species for which high-quality whole-genome sequence data are available, and hence a comprehensive and high-quality set of protein predictions exists. [R11] Reactome's own sentence about what that produces is printed beside the record: The electronically inferred reactions presented in Reactome are thus not data, but hypotheses useful to direct the design of confirmatory experiments. [R11]

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. [R11] Reactome, reactome.org. Computationally inferred events. https://reactome.org/documentation/inferred-events, read 2026-09-09.
  5. [R12] Reactome, reactome.org. Citing us. https://reactome.org/cite, read 2026-09-09.
  6. [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 mouse pathway

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

Genes Reactome places in this mouse pathway, page 1 of 1
GeneAaasAuthority223921Mapping file id223921 NCBI fileEvidenceIEA
GeneCalm1Authority12313Mapping file id12313 NCBI fileEvidenceIEA
GeneCalm2Authority12314Mapping file idENSMUSG00000036438 Ensembl fileEvidenceIEA
GeneCalm3Authority12315Mapping file idENSMUSG00000019370 Ensembl fileEvidenceIEA
GeneImpa1Authority55980Mapping file idENSMUSG00000027531 Ensembl fileEvidenceIEA
GeneImpa2Authority114663Mapping file id114663 NCBI fileEvidenceIEA
GeneInpp1Authority16329Mapping file id16329 NCBI fileEvidenceIEA
GeneInpp4aAuthority269180Mapping file id269180 NCBI fileEvidenceIEA
GeneInpp4bAuthority234515Mapping file id234515 NCBI fileEvidenceIEA
GeneInpp5aAuthority212111Mapping file id212111 NCBI fileEvidenceIEA
GeneInpp5bAuthority16330Mapping file id16330 NCBI fileEvidenceIEA
GeneInpp5dAuthority16331Mapping file id16331 NCBI fileEvidenceIEA
GeneInpp5jAuthority170835Mapping file id170835 NCBI fileEvidenceIEA
GeneInppl1Authority16332Mapping file id16332 NCBI fileEvidenceIEA
GeneIp6k1Authority27399Mapping file id27399 NCBI fileEvidenceIEA
GeneIp6k2Authority76500Mapping file id76500 NCBI fileEvidenceIEA
GeneIp6k3Authority271424Mapping file id271424 NCBI fileEvidenceIEA
GeneIpmkAuthority69718Mapping file id69718 NCBI fileEvidenceIEA
GeneIppkAuthority75678Mapping file id75678 NCBI fileEvidenceIEA
GeneIsyna1Authority71780Mapping file id71780 NCBI fileEvidenceIEA
GeneItpk1Authority217837Mapping file id217837 NCBI fileEvidenceIEA
GeneItpkaAuthority228550Mapping file id228550 NCBI fileEvidenceIEA
GeneItpkbAuthority320404Mapping file id320404 NCBI fileEvidenceIEA
GeneItpkcAuthority233011Mapping file id233011 NCBI fileEvidenceIEA
GeneMinpp1Authority17330Mapping file id17330 NCBI fileEvidenceIEA
GeneMioxAuthority56727Mapping file id56727 NCBI fileEvidenceIEA
GeneNdc1Authority72787Mapping file id72787 NCBI fileEvidenceIEA
GeneNudt10Authority102954Mapping file id102954 NCBI fileEvidenceIEA
GeneNudt11Authority58242Mapping file id58242 NCBI fileEvidenceIEA
GeneNudt3Authority56409Mapping file id56409 NCBI fileEvidenceIEA
GeneNudt4Authority71207Mapping file id71207 NCBI fileEvidenceIEA
GeneNup107Authority103468Mapping file id103468 NCBI fileEvidenceIEA
GeneNup133Authority234865Mapping file id234865 NCBI fileEvidenceIEA
GeneNup153Authority218210Mapping file id218210 NCBI fileEvidenceIEA
GeneNup155Authority170762Mapping file id170762 NCBI fileEvidenceIEA
GeneNup160Authority59015Mapping file id59015 NCBI fileEvidenceIEA
GeneNup188Authority227699Mapping file id227699 NCBI fileEvidenceIEA
GeneNup205Authority70699Mapping file id70699 NCBI fileEvidenceIEA
GeneNup210Authority54563Mapping file id54563 NCBI fileEvidenceIEA
GeneNup214Authority227720Mapping file id227720 NCBI fileEvidenceIEA
GeneNup35Authority69482Mapping file id69482 NCBI fileEvidenceIEA
GeneNup37Authority69736Mapping file id69736 NCBI fileEvidenceIEA
GeneNup42Authority231042Mapping file id231042 NCBI fileEvidenceIEA
GeneNup43Authority69912Mapping file id69912 NCBI fileEvidenceIEA
GeneNup50Authority18141Mapping file id18141 NCBI fileEvidenceIEA
GeneNup54Authority269113Mapping file id269113 NCBI fileEvidenceIEA
GeneNup58Authority71844Mapping file id71844 NCBI fileEvidenceIEA
GeneNup62Authority18226Mapping file id18226 NCBI fileEvidenceIEA
GeneNup85Authority445007Mapping file id445007 NCBI fileEvidenceIEA
GeneNup88Authority19069Mapping file id19069 NCBI fileEvidenceIEA
GeneNup93Authority71805Mapping file id71805 NCBI fileEvidenceIEA
GeneNup98Authority269966Mapping file id269966 NCBI fileEvidenceIEA
GeneOcrlAuthority320634Mapping file id320634 NCBI fileEvidenceIEA
GenePlcb1Authority18795Mapping file id18795 NCBI fileEvidenceIEA
GenePlcb2Authority18796Mapping file id18796 NCBI fileEvidenceIEA
GenePlcb3Authority18797Mapping file id18797 NCBI fileEvidenceIEA
GenePlcb4Authority18798Mapping file id18798 NCBI fileEvidenceIEA
GenePlcd1Authority18799Mapping file id18799 NCBI fileEvidenceIEA
GenePlcd3Authority72469Mapping file id72469 NCBI fileEvidenceIEA
GenePlcd4Authority18802Mapping file id18802 NCBI fileEvidenceIEA
GenePlce1Authority74055Mapping file id74055 NCBI fileEvidenceIEA
GenePlcg1Authority18803Mapping file id18803 NCBI fileEvidenceIEA
GenePlcg2Authority234779Mapping file id234779 NCBI fileEvidenceIEA
GenePlch1Authority269437Mapping file id269437 NCBI fileEvidenceIEA
GenePlch2Authority269615Mapping file id269615 NCBI fileEvidenceIEA
GenePlcz1Authority114875Mapping file id114875 NCBI fileEvidenceIEA
GenePld4Authority104759Mapping file id104759 NCBI fileEvidenceIEA
GenePom121Authority107939Mapping file id107939 NCBI fileEvidenceIEA
GenePpip5k1Authority327655Mapping file id327655 NCBI fileEvidenceIEA
GenePpip5k2Authority227399Mapping file id227399 NCBI fileEvidenceIEA
GenePtenAuthority19211Mapping file id19211 NCBI fileEvidenceIEA
GeneRae1Authority66679Mapping file id66679 NCBI fileEvidenceIEA
GeneRanbp2Authority19386Mapping file id19386 NCBI fileEvidenceIEA
GeneSec13Authority110379Mapping file id110379 NCBI fileEvidenceIEA
GeneSeh1lAuthority72124Mapping file id72124 NCBI fileEvidenceIEA
GeneSynj1Authority104015Mapping file id104015 NCBI fileEvidenceIEA
GeneTprAuthority108989Mapping file id108989 NCBI fileEvidenceIEA

Evidence codes on this page: IEA, 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: the two files disagree on none of the 87,729 mouse pairs both place.

  • Reactome mapping files, the mouse 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 mouse 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.