RDF/XMLNTriplesTurtleShow queryShare
SubjectPredicateObject
http://purl.uniprot.org/citations/12140292http://www.w3.org/1999/02/22-rdf-syntax-ns#typehttp://purl.uniprot.org/core/Journal_Citation
http://purl.uniprot.org/citations/12140292http://www.w3.org/2000/01/rdf-schema#comment"Leukotrienes are lipid mediators with important roles in immunity. The enzyme 5-lipoxygenase initiates leukotriene synthesis; nuclear import of 5-lipoxygenase modulates leukotriene synthetic capacity. In this study, we used structural and functional criteria to identify potential nuclear import sequences. Specifically, we sought basic residues that 1) were common to different 5-lipoxygenases but not shared with other lipoxygenases, 2) were found on random coil/loop structures, and 3) could be replaced without eliminating catalytic activity. Application of these criteria to the putative bipartite nuclear import sequence of 5-lipoxygenase revealed that this region formed an alpha-helix rather than a random coil, that the critical residue arginine 651 serves a structural role, and that mutation of this residue eliminated catalytic activity. A previously unrecognized region corresponding to residues 518-530 on human 5-lipoxygenase was found to be unique to 5-lipoxygenase and on a random coil. This region alone was sufficient to drive import of green fluorescent protein to the same degree as complete 5-lipoxygenase. Replacement of basic residues in this region of the complete protein was capable of eliminating nuclear import without abolishing catalytic activity. Surprisingly, two subpopulations of cells expressing 5-lipoxygenase with this mutated region could be discerned: those with strongly impaired import and those with normal import. Taken together, these results show that the previously identified region with a bipartite motif is not a functional import sequence, whereas the newly identified basic region constitutes a true nuclear import sequence. Moreover, we suggest that another sequence that can mediate nuclear import of 5-lipoxygenase remains to be identified."xsd:string
http://purl.uniprot.org/citations/12140292http://purl.org/dc/terms/identifier"doi:10.1074/jbc.m206070200"xsd:string
http://purl.uniprot.org/citations/12140292http://purl.uniprot.org/core/author"Luo M."xsd:string
http://purl.uniprot.org/citations/12140292http://purl.uniprot.org/core/author"Healy A.M."xsd:string
http://purl.uniprot.org/citations/12140292http://purl.uniprot.org/core/author"Jones S.M."xsd:string
http://purl.uniprot.org/citations/12140292http://purl.uniprot.org/core/author"Brock T.G."xsd:string
http://purl.uniprot.org/citations/12140292http://purl.uniprot.org/core/author"Peters-Golden M."xsd:string
http://purl.uniprot.org/citations/12140292http://purl.uniprot.org/core/date"2002"xsd:gYear
http://purl.uniprot.org/citations/12140292http://purl.uniprot.org/core/name"J Biol Chem"xsd:string
http://purl.uniprot.org/citations/12140292http://purl.uniprot.org/core/pages"38550-38556"xsd:string
http://purl.uniprot.org/citations/12140292http://purl.uniprot.org/core/title"Structural and functional criteria reveal a new nuclear import sequence on the 5-lipoxygenase protein."xsd:string
http://purl.uniprot.org/citations/12140292http://purl.uniprot.org/core/volume"277"xsd:string
http://purl.uniprot.org/citations/12140292http://www.w3.org/2004/02/skos/core#exactMatchhttp://purl.uniprot.org/pubmed/12140292
http://purl.uniprot.org/citations/12140292http://xmlns.com/foaf/0.1/primaryTopicOfhttps://pubmed.ncbi.nlm.nih.gov/12140292
http://purl.uniprot.org/uniprot/P48999#attribution-B0D8249CFA5725F2E0573D9A13171225http://purl.uniprot.org/core/sourcehttp://purl.uniprot.org/citations/12140292
http://purl.uniprot.org/uniprot/#_E9QA93-mappedCitation-12140292http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/12140292
http://purl.uniprot.org/uniprot/#_A0A0N4SW45-mappedCitation-12140292http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/12140292
http://purl.uniprot.org/uniprot/#_E9Q6H6-mappedCitation-12140292http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/12140292
http://purl.uniprot.org/uniprot/#_P48999-mappedCitation-12140292http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/12140292
http://purl.uniprot.org/uniprot/#_P09917-mappedCitation-12140292http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/12140292
http://purl.uniprot.org/uniprot/#_I0CLG0-mappedCitation-12140292http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/12140292
http://purl.uniprot.org/uniprot/#_Q3TC68-mappedCitation-12140292http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/12140292
http://purl.uniprot.org/uniprot/#_Q3TBK8-mappedCitation-12140292http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/12140292
http://purl.uniprot.org/uniprot/#_Q810M3-mappedCitation-12140292http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/12140292