hiraṇyagarbháḥ sám avartatā́gre bhūtásya jātáḥ pátir éka āsīt |
sá dādhāra pr̥thivī́m utá dyā́ṃ kásmai devā́ya havíṣā vidhema ||7||
The golden embryo was evolved (''sam-vṛt'') in the beginning; it was, when born, the sole lord of existence (''bhūtá''); it maintained earth and heaven - to what god may we pay worship with oblation?
William Dwight Whitney (revised and edited by Charles Rockwell Lanman)
The surface that matched
Each passage folds to its own comparison surface. Accents, word breaks and sandhi are removed before comparison.
hi̱ra̱ṇya̱ga̱rbhaḥ sam a̍varta̱tāgre̍ bhū̱tasya̍ jā̱taḥ pati̱r eka̍ āsīt | sa dā̍dhāra pṛthi̱vīṁ dyām u̱temāṁ kasmai̍ de̱vāya̍ ha̱viṣā̍ vidhema ||
IN the beginning rose Hiranyagarbha, born Only Lord of all created beings. He fixed and holdeth up this earth and heaven. What God shall we adore with our oblation?
Ralph T. H. Griffith
The surface that matched
Both passages fold to the same comparison surface. Accents, word breaks and sandhi are removed before comparison, so this string is not how either text reads.
These links are derived by comparing normalised Sanskrit surfaces. They show that two collections carry the same wording. They are not, by themselves, a demonstrated line of transmission between them, and the direction stored on an edge is a property of how it was built.
Yajurveda is one of four collections held here. Cross-corpus comparison bottoms out at the weakest shared surface, because a Devanagari text and a romanised text share no code points.
How these were derived2
Parallelism is symmetric and this graph stores it as a directed edge, so these relations are traversed in both directions and each row states which way the stored edge ran. All 1,684 REUSES_TEXT_FROM edges point Samaveda-to-Rigveda, and 1,421 Rigvedic passages have reuse edges only inbound; following the arrow would show those 1,421 verses no reuse at all.
measured
SHARES_ENTITY_VOCABULARY_WITH is not textual parallelism. It means two passages name some of the same registry concepts and says nothing about shared wording, so it is reported with relation_kind=ENTITY_VOCABULARY_OVERLAP and is excluded from textual_total.