Skip to content

Create an account and get up to 25% off.

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.

RNA Polymerase II Pre-transcription Events

R-MMU-674695 in Reactome release 97: under RNA Polymerase II Transcription, with 76 genes placed in it by the mapping files and 0 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-674695 (human), R-RNO-674695 (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 76 genes in this mouse pathway; showing 1 to 76, 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
GeneAff4Authority93736Mapping file id93736 NCBI fileEvidenceIEA
GeneCcnhAuthority66671Mapping file id66671 NCBI fileEvidenceIEA
GeneCcnt1Authority12455Mapping file id12455 NCBI fileEvidenceIEA
GeneCcnt2Authority72949Mapping file id72949 NCBI fileEvidenceIEA
GeneCdc73Authority214498Mapping file id214498 NCBI fileEvidenceIEA
GeneCdk7Authority12572Mapping file id12572 NCBI fileEvidenceIEA
GeneCdk9Authority107951Mapping file id107951 NCBI fileEvidenceIEA
GeneCtdp1Authority67655Mapping file id67655 NCBI fileEvidenceIEA
GeneCtr9Authority22083Mapping file id22083 NCBI fileEvidenceIEA
GeneEaf1Authority74427Mapping file id74427 NCBI fileEvidenceIEA
GeneEaf2Authority106389Mapping file id106389 NCBI fileEvidenceIEA
GeneEllAuthority13716Mapping file id13716 NCBI fileEvidenceIEA
GeneEloaAuthority27224Mapping file id27224 NCBI fileEvidenceIEA
GeneElobAuthority67673Mapping file id67673 NCBI fileEvidenceIEA
GeneElocAuthority67923Mapping file id67923 NCBI fileEvidenceIEA
GeneErcc2Authority13871Mapping file id13871 NCBI fileEvidenceIEA
GeneErcc3Authority13872Mapping file id13872 NCBI fileEvidenceIEA
GeneGtf2a1Authority83602Mapping file id83602 NCBI fileEvidenceIEA
GeneGtf2a2Authority235459Mapping file id235459 NCBI fileEvidenceIEA
GeneGtf2bAuthority229906Mapping file id229906 NCBI fileEvidenceIEA
GeneGtf2e1Authority74197Mapping file id74197 NCBI fileEvidenceIEA
GeneGtf2e2Authority68153Mapping file id68153 NCBI fileEvidenceIEA
GeneGtf2f1Authority98053Mapping file id98053 NCBI fileEvidenceIEA
GeneGtf2f2Authority68705Mapping file id68705 NCBI fileEvidenceIEA
GeneGtf2h1Authority14884Mapping file id14884 NCBI fileEvidenceIEA
GeneGtf2h2Authority23894Mapping file id23894 NCBI fileEvidenceIEA
GeneGtf2h3Authority209357Mapping file id209357 NCBI fileEvidenceIEA
GeneGtf2h4Authority14885Mapping file id14885 NCBI fileEvidenceIEA
GeneGtf2h5Authority66467Mapping file id66467 NCBI fileEvidenceIEA
GeneIws1Authority73473Mapping file id73473 NCBI fileEvidenceIEA
GeneLeo1Authority235497Mapping file id235497 NCBI fileEvidenceIEA
GeneMllt1Authority64144Mapping file id64144 NCBI fileEvidenceIEA
GeneMllt3Authority70122Mapping file id70122 NCBI fileEvidenceIEA
GeneMnat1Authority17420Mapping file id17420 NCBI fileEvidenceIEA
GeneNcbp1Authority433702Mapping file id433702 NCBI fileEvidenceIEA
GeneNcbp2Authority68092Mapping file id68092 NCBI fileEvidenceIEA
GeneNelfaAuthority24116Mapping file id24116 NCBI fileEvidenceIEA
GeneNelfbAuthority58202Mapping file id58202 NCBI fileEvidenceIEA
GeneNelfcdAuthority57314Mapping file id57314 NCBI fileEvidenceIEA
GeneNelfeAuthority27632Mapping file id27632 NCBI fileEvidenceIEA
GenePaf1Authority54624Mapping file id54624 NCBI fileEvidenceIEA
GenePolr2aAuthority20020Mapping file id20020 NCBI fileEvidenceIEA
GenePolr2bAuthority231329Mapping file id231329 NCBI fileEvidenceIEA
GenePolr2cAuthority20021Mapping file id20021 NCBI fileEvidenceIEA
GenePolr2dAuthority69241Mapping file id69241 NCBI fileEvidenceIEA
GenePolr2eAuthority66420Mapping file id66420 NCBI fileEvidenceIEA
GenePolr2fAuthority69833Mapping file id69833 NCBI fileEvidenceIEA
GenePolr2gAuthority67710Mapping file id67710 NCBI fileEvidenceIEA
GenePolr2hAuthority245841Mapping file id245841 NCBI fileEvidenceIEA
GenePolr2iAuthority69920Mapping file id69920 NCBI fileEvidenceIEA
GenePolr2kAuthority17749Mapping file id17749 NCBI fileEvidenceIEA
GenePolr2lAuthority66491Mapping file id66491 NCBI fileEvidenceIEA
GeneSkic8Authority66317Mapping file id66317 NCBI fileEvidenceIEA
GeneSsrp1Authority20833Mapping file id20833 NCBI fileEvidenceIEA
GeneSupt16Authority114741Mapping file id114741 NCBI fileEvidenceIEA
GeneSupt4aAuthority20922Mapping file id20922 NCBI fileEvidenceIEA
GeneSupt5Authority20924Mapping file id20924 NCBI fileEvidenceIEA
GeneSupt6Authority20926Mapping file id20926 NCBI fileEvidenceIEA
GeneTaf1Authority270627Mapping file id270627 NCBI fileEvidenceIEA
GeneTaf10Authority24075Mapping file id24075 NCBI fileEvidenceIEA
GeneTaf11Authority68776Mapping file id68776 NCBI fileEvidenceIEA
GeneTaf12Authority66464Mapping file id66464 NCBI fileEvidenceIEA
GeneTaf13Authority99730Mapping file id99730 NCBI fileEvidenceIEA
GeneTaf15Authority70439Mapping file id70439 NCBI fileEvidenceIEA
GeneTaf3Authority209361Mapping file id209361 NCBI fileEvidenceIEA
GeneTaf4Authority228980Mapping file id228980 NCBI fileEvidenceIEA
GeneTaf4bAuthority72504Mapping file id72504 NCBI fileEvidenceIEA
GeneTaf5Authority226182Mapping file id226182 NCBI fileEvidenceIEA
GeneTaf6Authority21343Mapping file id21343 NCBI fileEvidenceIEA
GeneTaf7Authority24074Mapping file id24074 NCBI fileEvidenceIEA
GeneTaf7lAuthority74469Mapping file id74469 NCBI fileEvidenceIEA
GeneTaf8Authority63856Mapping file id63856 NCBI fileEvidenceIEA
GeneTaf9Authority108143Mapping file id108143 NCBI fileEvidenceIEA
GeneTaf9bAuthority407786Mapping file id407786 NCBI fileEvidenceIEA
GeneTbpAuthority21374Mapping file id21374 NCBI fileEvidenceIEA
GeneTcea1Authority21399Mapping file id21399 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

Children

None: no pathway of this release's list names this one as a parent.

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.