Identification of a Novel Nuclear Localization Signal Common to 69- and 82-kDa Human Choline Acetyltransferase
Bibliographic record
Abstract
We demonstrated previously that 69- and 82-kDa human choline acetyltransferase are localized predominantly to the cytoplasm and the nucleus, respectively. We have now identified a nuclear localization signal common to both forms of enzyme using confocal microscopy to study the subcellular compartmentalization of choline acetyltransferase tagged with green fluorescent protein in living HEK 293 cells. To identify functional nuclear localization and export signals, portions of full-length 69-kDa choline acetyltransferase were cloned into the vector peGFP-N1 and the cellular distribution patterns of the fusion proteins observed. Of the nine constructs studied, one yielded a protein with nuclear localization and another produced a protein with cytoplasmic localization. Mutation of the critical amino acids in this novel putative nuclear localization signal in the 69- and 82-kDa enzymes demonstrated that it is functional in both proteins. Moreover, 69-kDa choline acetyltransferase but not the 82-kDa enzyme is transported out of the nucleus by the leptomycin B-sensitive Crm-1 export pathway. By using bikaryon cells expressing both 82-kDa choline acetyltransferase and the nuclear protein heterogeneous nuclear ribonucleoprotein with green and red fluorescent tags, respectively, we found that the 82-kDa enzyme does not shuttle out of the nucleus in measurable amounts. These data suggest that 69-kDa choline acetyltransferase is a nucleocytoplasmic shuttling protein with a predominantly cytoplasmic localization determined by a functional nuclear localization signal and unidentified putative nuclear export signal. For 82-kDa choline acetyltransferase, the presence of the unique amino-terminal nuclear localization signal plus the newly identified nuclear localization signal may be involved in a process leading to predominantly nuclear accumulation of this enzyme, or alternatively, the two nuclear localization signals may be sufficient to overcome the force(s) driving nuclear export.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.001 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".