conradry commited on
Commit
0a15406
·
verified ·
1 Parent(s): 90ab4ee

Add environmental-toxin overlay on the PD pathways

Browse files

pd_toxin_target.parquet (79 toxin-gene rows) and pd_toxin_pathway.parquet (76 pathways with toxin evidence rolled up), plus card sections covering the EC mapping, specificity weighting and the direction-of-effect caveat.

Files changed (3) hide show
  1. README.md +119 -2
  2. pd_toxin_pathway.parquet +3 -0
  3. pd_toxin_target.parquet +3 -0
README.md CHANGED
@@ -6,6 +6,7 @@ tags:
6
  - aidd
7
  - knowledge-graph
8
  - parkinsons-disease
 
9
  pretty_name: Biopharma hackathon data
10
  configs:
11
  - config_name: targets
@@ -24,6 +25,10 @@ configs:
24
  data_files: pd_subgraph_enrichment.parquet
25
  - config_name: pd_tree
26
  data_files: pd_tree.parquet
 
 
 
 
27
  ---
28
 
29
  # Biopharma hackathon data
@@ -33,9 +38,10 @@ and nothing joins them:
33
 
34
  1. **[GenomeScreen (relational)](#1-genomescreen-as-a-relational-dataset)** — 5 tables, the
35
  DrugCLIP genome-wide virtual screen parsed into parquet.
36
- 2. **[Parkinson's disease subgraph](#2-parkinsons-disease-subgraph-primekg)** — 3 tables, a
37
  pathway-centric neighbourhood extracted from PrimeKG, as a graph and as a
38
- disease→pathway→protein→drug tree.
 
39
 
40
  ---
41
 
@@ -153,6 +159,8 @@ enrichment table for filtering it down.
153
  | `pd_subgraph.parquet` | 162,384 | edge (both orientations — see below) |
154
  | `pd_subgraph_enrichment.parquet` | 283 | pathway |
155
  | `pd_tree.parquet` | 54,557 | root→leaf path, disease → pathway → protein → drug |
 
 
156
 
157
  ## How it was built
158
 
@@ -244,6 +252,65 @@ carry two relation types (usually enzyme + target), so they appear as two rows.
244
  The tree drops `protein_protein` and `pathway_pathway`, which have no place in a tree; use
245
  `pd_subgraph.parquet` for those.
246
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
247
  ## Caveats worth knowing before you use it
248
 
249
  - **Every edge in `pd_subgraph.parquet` appears twice.** PrimeKG stores undirected edges in
@@ -265,6 +332,39 @@ The tree drops `protein_protein` and `pathway_pathway`, which have no place in a
265
  protein interactions, not compounds with a PD rationale. Weight by target specificity, or
266
  restrict to a pathway you care about, before reading anything into the ordering.
267
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
268
  ## Usage
269
 
270
  ```python
@@ -294,6 +394,17 @@ conn.execute(f"""
294
  WHERE drug_relation = 'target' AND pathway_qvalue < 0.05
295
  GROUP BY 1 ORDER BY pathways DESC, proteins DESC LIMIT 25
296
  """).fetchall()
 
 
 
 
 
 
 
 
 
 
 
297
  ```
298
 
299
  ## Source and license
@@ -305,6 +416,12 @@ the data itself, which is distributed via Harvard Dataverse
305
  own ~20 constituent primary sources. Check those before redistributing. The `license` field in
306
  this repo's metadata (CC-BY-4.0) describes the GenomeScreen tables above.
307
 
 
 
 
 
 
 
308
  > Chandak, P., Huang, K., Zitnik, M. *Building a knowledge graph to enable precision medicine.*
309
  > Nature Scientific Data 10, 67 (2023).
310
 
 
6
  - aidd
7
  - knowledge-graph
8
  - parkinsons-disease
9
+ - toxicology
10
  pretty_name: Biopharma hackathon data
11
  configs:
12
  - config_name: targets
 
25
  data_files: pd_subgraph_enrichment.parquet
26
  - config_name: pd_tree
27
  data_files: pd_tree.parquet
28
+ - config_name: pd_toxin_target
29
+ data_files: pd_toxin_target.parquet
30
+ - config_name: pd_toxin_pathway
31
+ data_files: pd_toxin_pathway.parquet
32
  ---
33
 
34
  # Biopharma hackathon data
 
38
 
39
  1. **[GenomeScreen (relational)](#1-genomescreen-as-a-relational-dataset)** — 5 tables, the
40
  DrugCLIP genome-wide virtual screen parsed into parquet.
41
+ 2. **[Parkinson's disease subgraph](#2-parkinsons-disease-subgraph-primekg)** — 5 tables, a
42
  pathway-centric neighbourhood extracted from PrimeKG, as a graph and as a
43
+ disease→pathway→protein→drug tree, plus an environmental-toxin overlay on the same
44
+ pathways.
45
 
46
  ---
47
 
 
159
  | `pd_subgraph.parquet` | 162,384 | edge (both orientations — see below) |
160
  | `pd_subgraph_enrichment.parquet` | 283 | pathway |
161
  | `pd_tree.parquet` | 54,557 | root→leaf path, disease → pathway → protein → drug |
162
+ | `pd_toxin_target.parquet` | 79 | (environmental toxin, gene) |
163
+ | `pd_toxin_pathway.parquet` | 76 | pathway, with toxin evidence rolled up |
164
 
165
  ## How it was built
166
 
 
252
  The tree drops `protein_protein` and `pathway_pathway`, which have no place in a tree; use
253
  `pd_subgraph.parquet` for those.
254
 
255
+ ## The environmental-toxin overlay
256
+
257
+ A second, independent line of evidence on the same pathways. Ten environmental toxins with
258
+ an established PD association (paraquat, rotenone, MPTP, manganese, lead, mercury,
259
+ chlorpyrifos, dieldrin, trichloroethylene, tetrachloroethylene) were mapped to their
260
+ literature-co-mentioned gene targets, and those genes joined onto the tree's pathways.
261
+
262
+ The premise: a toxin that is *causative* for PD implicates the pathways it perturbs, so a
263
+ pathway reached by both the disease-association route and the toxicological route carries a
264
+ stronger prior than either alone. **9 of the 21 enriched pathways contain a toxin target**,
265
+ and the top of that list is the canonical PD tox story.
266
+
267
+ `pd_toxin_target.parquet` is one row per (toxin, gene): `toxin`, `cid`, `pubmed_mentions`,
268
+ `gene_symbol`, `protein_index` (PrimeKG), `evidence_count`, `n_source_entries`,
269
+ `source_entries`, `mapping_confidence`, `toxin_mapped_fraction`, `in_pd_tree`, `is_pd_seed`,
270
+ `tf`, `idf`, `specificity_weight`.
271
+
272
+ `pd_toxin_pathway.parquet` rolls that up per pathway and joins to `pd_tree.parquet` on
273
+ `pathway_index`: `n_toxins`, `n_toxin_targets`, `toxin_support`, `toxins`, `toxin_targets`,
274
+ alongside the pathway's `pathway_qvalue`, `n_drugs` and `n_target_drugs`.
275
+
276
+ Ranked by toxin support among pathways at q < 0.05:
277
+
278
+ | pathway | support | q | toxins | targets |
279
+ | --- | ---: | ---: | ---: | --- |
280
+ | Detoxification of Reactive Oxygen Species | 3.28 | 1.5e-02 | 6 | CAT, GPX1–3, SOD1–3 |
281
+ | Transcriptional activation of mitochondrial biogenesis | 2.99 | 2.4e-02 | 7 | GABPA, PPARGC1B, SOD2 |
282
+ | FOXO-mediated transcription of oxidative stress genes | 1.98 | 3.3e-02 | 6 | CAT, SOD2 |
283
+ | Interleukin-4 and Interleukin-13 signaling | 1.24 | 6.4e-03 | 4 | AKT1, BCL2, IL6, MAOA, TNF |
284
+ | Catecholamine biosynthesis | 1.05 | 1.6e-02 | 2 | TH |
285
+ | Biogenic amines deaminated by MAOA and MAOB | 0.19 | 6.4e-03 | 1 | MAOA, MAOB |
286
+
287
+ ### How the targets were mapped
288
+
289
+ The source lists targets as `name [TAG] (count)`, where TAG is a gene symbol *or* an EC
290
+ number. Three properties of that format shape the table:
291
+
292
+ - **The EC entries carry the mechanism.** MPTP's causal target is monoamine oxidase, which
293
+ appears only as `EC:1.4.3.4`; rotenone's is complex I, only as `EC:1.6.99.3`. Symbol-only
294
+ parsing loses both. EC classes are expanded through a hand-curated map, and
295
+ `mapping_confidence` records how firm each expansion is: `exact` (one human gene),
296
+ `family` (a small enumerated family — MAOA/MAOB, SOD1–3), or `complex` (complex I core
297
+ subunits). Large cross-species classes (`peroxidase`, `unspecific monooxygenase`) and
298
+ non-human ones (photosystem II, lignin peroxidase, bacterial dehalogenases) are dropped
299
+ rather than guessed at.
300
+ - **A toxin often lists one protein twice**, once by symbol and once by EC — lead has both
301
+ `catalase [CAT] (576)` and `catalase [EC:1.11.1.6] (234)`. Rows are aggregated to the
302
+ (toxin, gene) grain and the counts summed; `source_entries` preserves what contributed.
303
+ A family EC has its evidence split across members rather than replicated, so a family tag
304
+ cannot outvote a specific symbol.
305
+ - **The gene lists are cross-species.** Influenza PB2, bacterial MERA, rice LOC4326471 and a
306
+ *Drosophila* GABA receptor all appear. Only symbols resolving to a PrimeKG `gene/protein`
307
+ node are kept.
308
+
309
+ `specificity_weight` is `tf × idf`: a gene's share of its toxin's mapped evidence, damped by
310
+ how many toxins name it. CAT and the SODs appear for 6 of the 10 toxins — they are the
311
+ background of the toxicology literature, not a toxin-specific signal, and the weighting is
312
+ what keeps them from dominating.
313
+
314
  ## Caveats worth knowing before you use it
315
 
316
  - **Every edge in `pd_subgraph.parquet` appears twice.** PrimeKG stores undirected edges in
 
332
  protein interactions, not compounds with a PD rationale. Weight by target specificity, or
333
  restrict to a pathway you care about, before reading anything into the ordering.
334
 
335
+ - **PrimeKG's drug nodes are all of DrugBank, and it carries no approval status.** Every
336
+ `drug_id` is a `DB…` accession, but the set includes experimental entries, cofactors and
337
+ crystallographic ligands — NADH, copper and glutathione adducts all appear as `target`
338
+ drugs. There is no column to filter on; join against a DrugBank approval list if you need
339
+ approved compounds only.
340
+
341
+ Specific to the toxin overlay:
342
+
343
+ - **A shared target does not mean a shared direction of effect, and PrimeKG cannot tell you
344
+ which.** `drug_relation` distinguishes target from enzyme, never agonist from antagonist.
345
+ If a toxin causes PD by inhibiting a protein, a drug that also inhibits it is a risk, not a
346
+ therapy. `SLC6A3` is the clearest case: DAT-mediated uptake is how MPP+ enters dopaminergic
347
+ neurons, so a DAT blocker is protective while amphetamine — on the same target list — is
348
+ not. Read the overlay as nominating *pathways*, and get direction from DrugBank's action
349
+ field before selecting compounds within one.
350
+ - **The counts are literature co-mentions, not affinities or assays.** A high count means the
351
+ toxin and the gene are frequently discussed together, which tracks how well-studied a gene
352
+ is at least as much as how relevant it is.
353
+ - **The source lists only the top 8 of 25 targets per toxin.** Document frequencies — and so
354
+ every `idf` — are computed over that truncated view, which biases `idf` upward for genes
355
+ that fall below the cut for some toxins.
356
+ - **Two toxins are mostly unmappable.** `toxin_mapped_fraction` is 0.38 for tetrachloroethylene
357
+ and 0.40 for trichloroethylene; the rest of their lists is bacterial or fungal. Because `tf`
358
+ is a share of *mapped* evidence, the survivors absorb the whole share and their weights are
359
+ inflated. Treat anything below ~0.5 as soft.
360
+ - **`toxin_support` is a raw sum, so it rewards large pathways.** Unfiltered, `Neutrophil
361
+ degranulation` (478 proteins, q = 0.21) tops the ranking. The enrichment q-value already
362
+ controls for size — filter on it first, then rank by support.
363
+ - **10 toxin targets are absent from the tree entirely**, including all seven complex I core
364
+ subunits — the most PD-relevant mechanism in the set. They resolve to valid PrimeKG
365
+ `protein_index` values but sit in no PD-bridged pathway, so they contribute nothing to
366
+ `pd_toxin_pathway.parquet`. Filter `in_pd_tree = false` to see them.
367
+
368
  ## Usage
369
 
370
  ```python
 
394
  WHERE drug_relation = 'target' AND pathway_qvalue < 0.05
395
  GROUP BY 1 ORDER BY pathways DESC, proteins DESC LIMIT 25
396
  """).fetchall()
397
+
398
+ # convergent evidence: drugs targeting proteins in pathways that are both
399
+ # statistically enriched for PD proteins and hit by a PD-associated toxin
400
+ conn.execute(f"""
401
+ SELECT t.drug_name, t.protein_name, x.pathway_name,
402
+ x.toxins, x.toxin_support, x.pathway_qvalue
403
+ FROM '{base}/pd_tree.parquet' t
404
+ JOIN '{base}/pd_toxin_pathway.parquet' x USING (pathway_index)
405
+ WHERE t.drug_relation = 'target' AND x.pathway_qvalue < 0.05
406
+ ORDER BY x.toxin_support DESC, t.drug_name
407
+ """).fetchall()
408
  ```
409
 
410
  ## Source and license
 
416
  own ~20 constituent primary sources. Check those before redistributing. The `license` field in
417
  this repo's metadata (CC-BY-4.0) describes the GenomeScreen tables above.
418
 
419
+ The toxin overlay adds a second source: the toxin list and its gene targets come from
420
+ **PubChem** (compound records and their literature-co-mentioned genes) and PubMed mention
421
+ counts, retrieved via the PubChem PUG-REST API. PubChem aggregates from many depositors whose
422
+ individual terms vary; see https://www.ncbi.nlm.nih.gov/home/about/policies/. The EC-to-gene
423
+ map and the specificity weighting are original to this dataset.
424
+
425
  > Chandak, P., Huang, K., Zitnik, M. *Building a knowledge graph to enable precision medicine.*
426
  > Nature Scientific Data 10, 67 (2023).
427
 
pd_toxin_pathway.parquet ADDED
@@ -0,0 +1,3 @@
 
 
 
 
1
+ version https://git-lfs.github.com/spec/v1
2
+ oid sha256:92109720302c81997dbb3e65595a030303872618270b5e447fcb7e4ba1be98fb
3
+ size 8426
pd_toxin_target.parquet ADDED
@@ -0,0 +1,3 @@
 
 
 
 
1
+ version https://git-lfs.github.com/spec/v1
2
+ oid sha256:679966d87a76403c24a67b1c6751f15d9d6dc58c883059f97dbde09991b2c2db
3
+ size 8037