Skip to content

Create an account and get up to 25% off.

Order

Pathway Human Homo sapiens

Global Genome Nucleotide Excision Repair (GG-NER)

R-HSA-5696399 in Reactome release 97: under Nucleotide Excision Repair, with 84 genes placed in it by the mapping files and 4 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-5696399 (mouse), R-RNO-5696399 (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 84 genes in this human pathway; showing 1 to 84, 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
GeneACTBAuthorityHGNC:132Mapping file id60 NCBI fileEvidenceTAS
GeneACTL6AAuthorityHGNC:24124Mapping file id86 NCBI fileEvidenceTAS
GeneACTR5AuthorityHGNC:14671Mapping file id79913 NCBI fileEvidenceTAS
GeneACTR8AuthorityHGNC:14672Mapping file id93973 NCBI fileEvidenceTAS
GeneCCNHAuthorityHGNC:1594Mapping file id902 NCBI fileEvidenceTAS
GeneCDK7AuthorityHGNC:1778Mapping file id1022 NCBI fileEvidenceTAS
GeneCETN2AuthorityHGNC:1867Mapping file id1069 NCBI fileEvidenceTAS
GeneCHD1LAuthorityHGNC:1916Mapping file id9557 NCBI fileEvidenceTAS
GeneCOPS2AuthorityHGNC:30747Mapping file id9318 NCBI fileEvidenceTAS
GeneCOPS3AuthorityHGNC:2239Mapping file id8533 NCBI fileEvidenceTAS
GeneCOPS4AuthorityHGNC:16702Mapping file id51138 NCBI fileEvidenceTAS
GeneCOPS5AuthorityHGNC:2240Mapping file id10987 NCBI fileEvidenceTAS
GeneCOPS6AuthorityHGNC:21749Mapping file id10980 NCBI fileEvidenceTAS
GeneCOPS7AAuthorityHGNC:16758Mapping file id50813 NCBI fileEvidenceTAS
GeneCOPS7BAuthorityHGNC:16760Mapping file id64708 NCBI fileEvidenceTAS
GeneCOPS8AuthorityHGNC:24335Mapping file id10920 NCBI fileEvidenceTAS
GeneCUL4AAuthorityHGNC:2554Mapping file id8451 NCBI fileEvidenceTAS
GeneCUL4BAuthorityHGNC:2555Mapping file id8450 NCBI fileEvidenceTAS
GeneDDB1AuthorityHGNC:2717Mapping file id1642 NCBI fileEvidenceTAS
GeneDDB2AuthorityHGNC:2718Mapping file id1643 NCBI fileEvidenceTAS
GeneERCC1AuthorityHGNC:3433Mapping file id2067 NCBI fileEvidenceTAS
GeneERCC2AuthorityHGNC:3434Mapping file id2068 NCBI fileEvidenceTAS
GeneERCC3AuthorityHGNC:3435Mapping file id2071 NCBI fileEvidenceTAS
GeneERCC4AuthorityHGNC:3436Mapping file id2072 NCBI fileEvidenceTAS
GeneERCC5AuthorityHGNC:3437Mapping file id2073 NCBI fileEvidenceTAS
GeneGPS1AuthorityHGNC:4549Mapping file id2873 NCBI fileEvidenceTAS
GeneGTF2H1AuthorityHGNC:4655Mapping file id2965 NCBI fileEvidenceTAS
GeneGTF2H2AuthorityHGNC:4656Mapping file id2966 NCBI fileEvidenceTAS
GeneGTF2H3AuthorityHGNC:4657Mapping file id2967 NCBI fileEvidenceTAS
GeneGTF2H4AuthorityHGNC:4658Mapping file id2968 NCBI fileEvidenceTAS
GeneGTF2H5AuthorityHGNC:21157Mapping file id404672 NCBI fileEvidenceTAS
GeneINO80AuthorityHGNC:26956Mapping file id54617 NCBI fileEvidenceTAS
GeneINO80BAuthorityHGNC:13324Mapping file id83444 NCBI fileEvidenceTAS
GeneINO80CAuthorityHGNC:26994Mapping file id125476 NCBI fileEvidenceTAS
GeneINO80DAuthorityHGNC:25997Mapping file id54891 NCBI fileEvidenceTAS
GeneINO80EAuthorityHGNC:26905Mapping file id283899 NCBI fileEvidenceTAS
GeneLIG1AuthorityHGNC:6598Mapping file id3978 NCBI fileEvidenceTAS
GeneLIG3AuthorityHGNC:6600Mapping file id3980 NCBI fileEvidenceTAS
GeneMCRS1AuthorityHGNC:6960Mapping file id10445 NCBI fileEvidenceTAS
GeneMNAT1AuthorityHGNC:7181Mapping file id4331 NCBI fileEvidenceTAS
GeneNFRKBAuthorityHGNC:7802Mapping file id4798 NCBI fileEvidenceTAS
GenePARP1AuthorityHGNC:270Mapping file id142 NCBI fileEvidenceTAS
GenePARP2AuthorityHGNC:272Mapping file id10038 NCBI fileEvidenceTAS
GenePCNAAuthorityHGNC:8729Mapping file id5111 NCBI fileEvidenceTAS
GenePIAS1AuthorityHGNC:2752Mapping file id8554 NCBI fileEvidenceTAS
GenePIAS3AuthorityHGNC:16861Mapping file id10401 NCBI fileEvidenceTAS
GenePOLD1AuthorityHGNC:9175Mapping file id5424 NCBI fileEvidenceTAS
GenePOLD2AuthorityHGNC:9176Mapping file id5425 NCBI fileEvidenceTAS
GenePOLD3AuthorityHGNC:20932Mapping file id10714 NCBI fileEvidenceTAS
GenePOLD4AuthorityHGNC:14106Mapping file id57804 NCBI fileEvidenceTAS
GenePOLEAuthorityHGNC:9177Mapping file id5426 NCBI fileEvidenceTAS
GenePOLE2AuthorityHGNC:9178Mapping file id5427 NCBI fileEvidenceTAS
GenePOLE3AuthorityHGNC:13546Mapping file id54107 NCBI fileEvidenceTAS
GenePOLE4AuthorityHGNC:18755Mapping file id56655 NCBI fileEvidenceTAS
GenePOLKAuthorityHGNC:9183Mapping file id51426 NCBI fileEvidenceTAS
GeneRAD23AAuthorityHGNC:9812Mapping file id5886 NCBI fileEvidenceTAS
GeneRAD23BAuthorityHGNC:9813Mapping file id5887 NCBI fileEvidenceTAS
GeneRBX1AuthorityHGNC:9928Mapping file id9978 NCBI fileEvidenceTAS
GeneRFC1AuthorityHGNC:9969Mapping file id5981 NCBI fileEvidenceTAS
GeneRFC2AuthorityHGNC:9970Mapping file id5982 NCBI fileEvidenceTAS
GeneRFC3AuthorityHGNC:9971Mapping file id5983 NCBI fileEvidenceTAS
GeneRFC4AuthorityHGNC:9972Mapping file id5984 NCBI fileEvidenceTAS
GeneRFC5AuthorityHGNC:9973Mapping file id5985 NCBI fileEvidenceTAS
GeneRNF111AuthorityHGNC:17384Mapping file id54778 NCBI fileEvidenceTAS
GeneRPA1AuthorityHGNC:10289Mapping file id6117 NCBI fileEvidenceTAS
GeneRPA2AuthorityHGNC:10290Mapping file id6118 NCBI fileEvidenceTAS
GeneRPA3AuthorityHGNC:10291Mapping file id6119 NCBI fileEvidenceTAS
GeneRPS27AAuthorityHGNC:10417Mapping file id6233 NCBI fileEvidenceTAS
GeneRUVBL1AuthorityHGNC:10474Mapping file id8607 NCBI fileEvidenceTAS
GeneSUMO1AuthorityHGNC:12502Mapping file id7341 NCBI fileEvidenceTAS
GeneSUMO2AuthorityHGNC:11125Mapping file id6613 NCBI fileEvidenceTAS
GeneSUMO3AuthorityHGNC:11124Mapping file id6612 NCBI fileEvidenceTAS
GeneTFPTAuthorityHGNC:13630Mapping file id29844 NCBI fileEvidenceTAS
GeneUBA52AuthorityHGNC:12458Mapping file id7311 NCBI fileEvidenceTAS
GeneUBBAuthorityHGNC:12463Mapping file id7314 NCBI fileEvidenceTAS
GeneUBCAuthorityHGNC:12468Mapping file id7316 NCBI fileEvidenceTAS
GeneUBE2IAuthorityHGNC:12485Mapping file id7329 NCBI fileEvidenceTAS
GeneUBE2NAuthorityHGNC:12492Mapping file id7334 NCBI fileEvidenceTAS
GeneUBE2V2AuthorityHGNC:12495Mapping file id7336 NCBI fileEvidenceTAS
GeneUSP45AuthorityHGNC:20080Mapping file id85015 NCBI fileEvidenceTAS
GeneXPAAuthorityHGNC:12814Mapping file id7507 NCBI fileEvidenceTAS
GeneXPCAuthorityHGNC:12816Mapping file id7508 NCBI fileEvidenceTAS
GeneXRCC1AuthorityHGNC:12828Mapping file id7515 NCBI fileEvidenceTAS
GeneYY1AuthorityHGNC:12856Mapping file id7528 NCBI fileEvidenceTAS

Evidence codes on this page: 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.