Skip to content
VedAnvaya

The material world

What the four collections name, and in which of them. Every figure is a Sanskrit lexical minimum: a lower bound produced by a registered set of word forms.

Things listed
5
Collections read
4
Every figure is
Partial coverage
Named things by collection, with the status of each cell.
Named thingKindRigvedaSamavedaYajurvedaAtharvavedaTotal
Turvasha (turvaśa)Tribe113no match115
Purus (pūru)Tribe9no matchno match110
Bharatas (bharata)Tribe51118
Yadu (yadu)Tribe6no matchno matchno match6
Trtsus (tṛtsu)Tribe3no matchno matchno match3

Gaps we know are wrong

Cells the matcher cannot reach even though the corpus names the thing. They are declared here rather than left to read as an absence.

  • metal (ayas) in YajurvedaNo lexical match

    NO_LEXICAL_MATCH, and knowingly wrong. metal (ayas) is named in this corpus at VSM 18.13, the verse this graph measures as naming the most metals in it (5 reached there: copper (loha), dark metal (śyāma), gold (hiraṇya), lead (sīsa), tin (trapu)). No alias reaches it here: the elided form folds to a token that is the relative pronoun in almost all of its corpus occurrences, so registering it would land wrong-sense mentions instead of one right one. This cell is therefore NOT '0 occurrences' and NOT 'absent from this Veda'. The full lexical reason is the caveat sourced 'metals_by_veda'.

    Named at VSM 18.13, in the same verse as copper (loha), dark metal (śyāma), gold (hiraṇya), lead (sīsa), tin (trapu).

The metals grid returned 28 of 28 cells: 15 lexical minimum, 13 no lexical match.

See every recorded limit of this build

How these counts were measured2
  • Five tribes, 42 mentions. Published separately from rivers_and_tribes because the join of the two is empty: the tribes are attested and the rivers are attested, and they never share a mantra in this corpus.

    tribes_mentioned
  • The lexical mention layer reaches all four corpora, so a corpus with no figure had no registered alias match rather than no coverage. A null is still not a zero: alias recall is partial and measured per entity, not assumed.

    measured
Notes on the metals grid4
  • Every metal is returned against every Veda, so a cell that found nothing says NO_LEXICAL_MATCH in its own row rather than going missing: absence here is a fact about the matcher, never about the text. That distinction is load-bearing and there is a known false cell. The Yajurveda names ayas at VSM 18.13, where the Devanagari source writes it with avagraha elision (`me `yas ca me`) and it folds to the token `yasca`, which is the relative pronoun in 11 of its 12 corpus occurrences; registering it would land 11 wrong-sense mentions, so ayas reads NO_LEXICAL_MATCH for YV although that verse names it. `ayo` was rejected on the same precision test -- 6 token hits, of which only about half are the metal. Aliases are whole-word inflections only: the bare stem `ayas` substring-matches 645 times inside payasa/madayasva, and the bare `syama` token-matches a verb form at RV 6.5.7 and sits inside asyama 22 times, so only the attested `syamam`/`syamam` forms are admitted. Counts are lower bounds. `per_1000_mantras` is the figure to compare Vedas on, and it reorders the raw counts: gold is RV 38 against AV 34 raw but 3.601 against 5.823 normalised.

    metals_by_veda
  • Every registered metal is returned against every corpus, so no cell is omitted. A cell with no lexical match carries a null count and NO_LEXICAL_MATCH rather than 0: the registry admits attested whole-word inflections only, so the miss is a fact about the matcher.

    measured
  • Known-wrong cells, typed in their own rows and not only here: metal (ayas) in YV, attested at VSM 18.13. Read each cell's source_witness before concluding an absence.

    measured
  • Normalising reorders gold (hiraṇya), lead (sīsa): each of those rows ranks corpora differently raw than per 1,000 mantras, and the row states both orderings.

    measured