Fast accumulators of tau have higher levels of plasma pTau and stronger associations with amyloid in later Braak regions at baseline
Bibliographic record
Abstract
Abstract Background Accumulation of tau neurofibrillary tangles in Alzheimer’s disease (AD) follows a stereotypical pattern, known as Braak staging. As individuals show different rates of tau accumulation, depending on their initial stage, this potentially biases drug effects on tau pathology over time. We hypothesized that amyloid would be a driving force behind tau deposition in later Braak regions for those that were at earlier stages of the disease. Method 79 individuals (CU: 57, MCI: 21, AD: 1) were recruited from the Translational Biomarkers of Aging and Dementia (TRIAD) cohort. All individuals underwent baseline and 2‐year follow‐up amyloid ([18F]AZD4694) and tau ([18F]MK6240) PET imaging, as well as baseline plasma pTau181, pTau217, and pTau231 assessments. Differences in standardized uptake value ratios between the two timepoints in Braak I‐IV were used to separate fast accumulators of tau from slow accumulators, using the standard deviation of a Young group (n = 13). Pearson R’s were calculated between tau deposition in Braak regions IV‐VI and the neocortical amyloid load at baseline, within both these groups. Furthermore, a voxelwise analysis was performed to identify specific regional differences in amyloid SUVR between slow and fast progressors, while correcting for age, sex, ApoE4 carriership, as well as the individual’s Braak stage. In addition, an independent t‐test was performed to compare the levels of each pTau species at baseline. Result Fast accumulators had stronger increases (p < 0.01) in tau accumulation in Braak region V and VI, compared to slower accumulators. Furthermore, the level of tau deposition in Braak region IV and V was positively associated (p < 0.01) with the amyloid load in the neocortex, but only in the fast accumulator group (figure 1). The voxelwise analysis confirmed that faster progressors had stronger associations with amyloid‐PET (figure 2). Furthermore, those who accumulated tau at a faster rate also had higher levels of plasma pTau at baseline (figure 3). Conclusion Tau deposition in later Braak regions is associated with a higher amyloid load and increased values of pTau181, pTau217 and pTau231 at baseline in individuals in early Braak stages that accumulate tau at a more rapid rate.
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.001 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.003 | 0.000 |
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".