Display Settings:

Format

Send to:

Choose Destination
We are sorry, but NCBI web applications do not support your browser and may not function properly. More information
Eur J Biochem. 1998 Mar 15;252(3):542-52.

Sequential phosphorylation of Tau by glycogen synthase kinase-3beta and protein kinase A at Thr212 and Ser214 generates the Alzheimer-specific epitope of antibody AT100 and requires a paired-helical-filament-like conformation.

Author information

  • 1Max-Planck-Unit for Structural Molecular Biology, Hamburg, Germany.

Abstract

AT100 is a monoclonal antibody highly specific for phosphorylated Tau in Alzheimer paired helical filaments. Here we show that the epitope is generated by a complex sequence of sequential phosphorylation, first of Ser199, Ser202 and Thr205 (around the epitope of antibody AT8), next of Thr212 by glycogen synthase kinase (GSK)-3beta (a proline-directed kinase), then of Ser214 by protein kinase A (PKA). Conversely, if Ser214 is phosphorylated first it protects Thr212 and the Ser-Pro motifs around the AT8 site against phosphorylation, and the AT100 epitope is not formed. The generation of the AT100 epitope requires a conformation of tau induced by polyanions such as heparin, RNA or poly(Glu), conditions which also favor the formation of paired helical filaments. The Alzheimer-like phosphorylation can be induced by brain extracts. In the extract, the kinases responsible for generating the AT100 epitope are GSK-3beta and PKA, which can be inhibited by their specific inhibitors LiCl and RII, respectively. A cellular model displaying the reaction with AT100 is presented by Sf9 insect cells transfected with Tau. Knowledge of the events and kinases generating the AT100 epitope in cells might allow us to study the degeneration of the cytoskeleton in Alzheimer's disease.

PMID:
9546672
[PubMed - indexed for MEDLINE]
Free full text
PubMed Commons home

PubMed Commons

0 comments
How to join PubMed Commons

    Supplemental Content

    Full text links

    Icon for Blackwell Publishing
    Loading ...
    Write to the Help Desk