condition

visalpaka

visalpaka (visalpaka)

A named Atharvavedic ailment of the limbs, ears and eyes, ejected together with the abscess and the heart-disease; left untranslated because the corpus gives its sites and its remedy and not its nature.

Supported

Affliction

Open in the graph Ask about visalpaka (visalpaka)

Corpus reach

Passages reached

Passages that reach this record through the lexical, conceptual or ritual predicates this surface counts.

Passages reached. Passages that reach this record through the lexical, conceptual or ritual predicates this surface counts.
Rigveda	Insufficient evidence	not established
Samaveda	Insufficient evidence	not established
Yajurveda	Insufficient evidence	not established
Atharvaveda		4

A null is not a zero: it means this object was not reached in that corpus by the lexical, conceptual or ritual predicates counted here. The mention layer's measured recall is 0.8857, so even a reached corpus is a lower bound.

Other names

visalpakamvisalpakaḥvisalpakaṃvisalpasya

How this record was built4

Filtered to condition_kind=AFFLICTION: 26 of the 36 Condition nodes. The 8 THREAT entries (demons, sorcery, curses) and 2 PATHOGEN_OR_CAUSE entries (worms, poison) are excluded, because a disease list that returns a demon is a category error and not a rounding error. Ask kind=ANY to see all three, and read the `kind` on every row.
measured
CORRECTED IN V3.2: this query asked an affliction question and answered it with demons. Of the 718 MENTIONS_ENTITY edges reaching a Condition, 314 reached a THREAT and 88 a PATHOGEN_OR_CAUSE, so rakshas, sorcery, curses, worms and poison were all ranking as diseases. The 8 THREAT and 2 PATHOGEN_OR_CAUSE conditions are now excluded here by `condition_kind` and remain reachable through passages_protecting_against and condition_neighbourhood, both of which stay deliberately broad. Naming an affliction is weaker than treating it. CORRECTED IN V3.1: this caveat read 'There is deliberately no separate fever entity: takman- forms sit in YAKSMA-DISEASE'. That is no longer true -- VG:CONCEPT:TAKMAN-FEVER exists and carries 33 mentions -- so the caveat was denying the existence of an entity the same database returns. The reason it originally gave still matters, and is now a live hazard rather than a settled policy: the takman- paradigm is split across two entities, so a query filtering on either alone undercounts fever. Read TAKMAN-FEVER and YAKSMA-DISEASE together, and treat the split as unmeasured until someone reconciles the paradigm.
conditions_treated
`passage_count` counts DISTINCT passages reaching the object through the lexical, conceptual and ritual predicates this surface counts, and is the same figure the detail view reports. It is NULL, never 0, where no passage reaches it: the mention layer's measured recall is 0.8857, so a null is a lower bound and not an assertion that the corpus is silent.
measured
`co_mentioned` is CO-OCCURRENCE WITHIN A MANTRA and nothing more. It carries no causal, prescriptive or pharmacological claim: a plant named beside an affliction is named beside it, and apamarga is named against sorcery rather than against a cough. `neighbours` holds the curated edges, which are a different strength of claim; the two are separate fields so they cannot be read as one.
measured

Direct relationships

Named in the same verses