Effect of the Interaction Between Lipoxygenase Pathway and Progesterone on the Regulation of Hydroxysteroid 11-Beta Dehydrogenase 2 in Cultured Human Term Placental Trophoblasts1
Bibliographic record
Abstract
Placental hydroxysteroid 11-beta dehydrogenase 2 (HSD11B2) plays an important role in pregnancy maintenance and fetal maturation. In the event of intrauterine infection, lipoxygenase (LOX) metabolites are produced in the placenta and contribute to preterm labor and adverse fetal outcomes. On the other hand, LOX metabolites are involved in production of progesterone, which is required for pregnancy maintenance. In this study, we evaluated the interaction between the LOX pathway, progesterone, and HSD11B2. Specifically, we hypothesized that LOX metabolites would alter HSD11B2 and this effect would be mediated by progesterone. We cultured human term placental trophoblasts in the presence and absence of the LOX inhibitors Nordihydroguaiaretic acid (NDGA), AA861, and Baicalein; the LOX metabolites Leukotriene B(4) and 12(S)-Hydroxyeicosatetraenoate (12-HETE); and progesterone and progesterone receptor antagonist RU486. By radiometric conversion assay, real-time quantitative PCR, Western blot analysis, and ELISA, we examined HSD11B2 enzyme activity, HSD11B2 mRNA and HSD11B2 protein expression, and progesterone output. LOX metabolites down-regulated HSD11B2 activity and HSD11B2 expression. LOX inhibitors up-regulated HSD11B2 activity and HSD11B2 and HSD11B2 expression, and these effects were attenuated by addition of LOX metabolites. Net progesterone output was increased by LOX metabolites and decreased by LOX inhibitors. Progesterone down-regulated HSD11B2 activity and HSD11B2 and HSD11B2 expression, and these effects were blocked by RU486. Furthermore, the suppressive effect of 12-HETE on HSD11B2 activity was also reversed by RU486. We conclude that HSD11B2 in human placental trophoblasts is decreased by progesterone and increased by inhibition of endogenous LOX metabolites, and that a component of the effect of LOX metabolites on HSD11B2 is mediated by their stimulation of endogenous progesterone output.
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.001 | 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.001 |
| Insufficient payload (model declined to judge) | 0.002 | 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".