summary of the verb building rulesmmmmmmmmm ^ C- 1696

The rules that assemble verbs work in four stages --

(1) choose a root with the appropriate meaning, and a tense

(2) decide if you want the verb to be kartari or akartari. You may always choose freely. This does not affect the meaning of the sentence.

If you have chosen kartari, your next step is --

(3K) find out the person and number of the doer of the root and grab from the tiG list the two tiG that have that person and number, one flat and one bent. Depending on which root it is, we'll have to take always the flat, always the bent, or choose freely. Replace the tense with that tiG.

However if you have chosen akartari, the next step is --

(3AK) find the person and number of the object of the root, and grab the bent tiG that has that person and number. If the root is objectless, just choose ta. Replace the tense with that tiG.

Either way, we are done choosing, the next step is --

(4) there is a bunch of rules that must work automatically and will maybe change the root, change the tiG, or combine the two pieces.

There are hundreds of these rules, but don't panic. You don't need to know them yet. While you don't know all, you can cheat and use the inria tools to see the effects of the rules. The rules are important for the guys that build the inria tools.

After that,

(A) if we chose a kartari verb the object of the verb gets a second affix, and no rule says what case the doer of the verb gets (when in doubt, use the first),

(B) but if we chose an akartari verb, the doer gets third. If there is an object, no rule says what case the object gets.

Examples --

king is cooking rice

I am eating bananas

I'm sitting

the monkeys will hate the two men

king is cooking ricemmmmmmmmm ^ C- 1697

Suppose you want to say "king is cooking rice". You need a nounbase for "king", such as nRpa- or rAjan-, both m, and a nounbase for the rice, for instance taNDula- "rice grain" m.

(1) choose a root for cooking, for instance pac. Choose a tense, for instance laT, to mean that the cooking is happening now.

(2) this time we choose to build a kartari verb.

(3) the doer is the king, who is singular and third person. The two singular third person affixes in the list tiptas are flat tip and bent ta. After the root pac, we must use the bent if the king is planning to eat the rice himself, or the flat if he plans to feed someone else. Lets choose the flat. So far we have --

pac + laT → pac + tip

(4) Now the automatic rules work. There is a rule kartarizap that adds zap after pac. The rule works because tip is a hard affix and it is a kartari affix (was chosen according to the doer). So we have --

pac + laT → pac + tip →kartarizap pac + zap + tip → pacati "he is cooking"

We can use that verb to make the sentence --

taNDulAn pacati nRpaH "king is cooking rice grains"

Here the object of the verb, taNDula-, got a second affix, zas, because rule karmaNidvi says that the object gets second when the verb is kartari. As no rule says which case must be added after the doer of a kartari verb, here we added after "king" a first affix, su.

If in step (2) we decide to use an akartari affix, then instead of step (3K) we do step (3AK). We must choose a tiG that is bent and has the same number and person as the object, that is, as the rice grains. So we need to use jha, which is bent, plural and third person.

pac + laT → pac + jha

Now in step 4, some rules change the root pac into pacya, other rules change the tense jha into ante, and then the general joining rule atoguNe joins the two a of pacya and ante into one a --

pac + laT → pac + jha → pac + yak + jha → pacya + jha →Tita pacya + jhe →jhontaH pacya + ante →atoguNe pacyante

And with this verb we can build the sentence

nRpeNa taNDulAH pacyante "king is cooking rice grains"

See also difference between kartari and akartari verbs .

I am eating bananasmmmmmmmmm ^ C- 1699

(1) Choose a root for eating, for instance ad or bhuj. Choose a tense. Here we use laT to mean I'm eating right now.

(2) again we choose to make a kartari verb.

(3) Our doer (the one doing the eating) is me, which is first person and singular. So we need a first person singular tiG affix. There are two such affixes, the flat is mip and the bent is iT'. After the root ad we cannot choose which one we want, we must always use the flat. So we need mip.

(4) Our pieces are --

ad + laT → ad + mip

This time no rules change the root or on the tiG, so we are already done; we just have to remove the label p --

ad + laT → ad + mip → admi "I'm eating"

(the kartarizap rule did not work this time because exception adipra says it doesn't work after ad.)

With this verb we can build sentences like

admi kadalIphalAni "I'm eating bananas"

or

aham admi kadalIphalAni "me, I'm eating bananas"

Here the object is kadalIphalAni and it got zas because its the object of a kartari verb, so it needs a second, one of amauTchaS. It got zas because there are at least three bananas.

The doer is aham, which is built from the nounbase asmad- by adding the first affix su. We used a first affix because no rule here tells us to use any other case. When the doer is aham, and the verb shows by its mip affix that the doer is aham, the word aham may appear in the sentence, but it usually doesn't.

Now, if in step (2) we decide to make an akartari verb, then the tense replacement must be a bent affix that shows the person and number of the object, the bananas That is the third person plural bent affix jha.

ad + laT → ad + akartari jha → ad + yak + jha →Tita ad + ya + jhe →jhontaH ad + yak + ante →AdguNaH adyante

No rule says which case the object of an akartari verb must get, so we use a first ending, one of su au jas. As there are three or more bananas, we use jas. As for the doer, who is me, it must get a third ending by rule kartRkaraNa. As me is singular, it gets TA. Joining asmad- and TA we get mayA by a series of complicated rules. So our sentence is

adyante mayA kadalIphalAni "I am eating bananas"

Including the word mayA in the sentence is not necessary, but if we don't include it, then we are not saying who the doer is --

adyante kadalIphalAni "someone is eating bananas, bananas are being eaten"

the monkeys will hate the two menmmmmmmmmm ^ C- 1701

doer: the monkeys (kapi- plural)

object: the two men (nara- dual)

(1) root for hate: dviS; tense lRT (one of the two future tenses)

(2) we choose kartari

(3) the doer is third person plural so the tense must be replaced with flat jhi or with bent jha. After the root dviS, we can choose freely one or the other. Let's choose jha.

(4) As for the automatic rules, here rule syatAsI adds sya after the root. The jha ending turns into /jhe by Tita and then into ante by jhontaH. Now dviS becomes dveS because of rule puganta, Ss becomes kS by rule SaDhoHkassi, and atoguNe replaces two a with one --

dviS + lRT → dviS + jha → dviS + sya + jha → dviS + sya + jhe → dviS + sya + ante → dveS + sya + ante → dvekSya + ante → dvekSyante "they will hate"

If we had chosen jhi instead of jha, the rules would have made dvekSyanti, same meaning "they will hate".

Now when assembling the sentence, the nounbase nara- "man" for the object gets the dual affix of the second group, which is au, and the doer kapi- "monkey" gets the plural affix of the first group, which is jas. So we say --

narau dvekSyante kapayaH "the monkeys will hate the two men"

What if we choose to make an akartari verb? In step (3), we need a bent affix. That affix will be third person and dual because the object is third person and dual. So it will be AtAm. This AtAm is still a lRT replacer, so the root still gets sya added. The root still gets puganta change before sya. We still got Ss so the kS change still works. The AtAm becomes Ate by Tita. And then we have an a before the A of AtAm, so rule AtoGitaH turns those two into e --

dviS + lRT → dviS + karmaNi AtAm → dviS + sya + AtAm → dveS + sya + AtAm → dveS + sya + Ate → dvekSya + Ate →AtoGitaH dvekSyete

When assembling the sentence, this time the doer kapi- gets the plural affix of the third group, which is bhis, and the object nara- gets the dual affix of the first group. So we say

narau dvekSyete kapibhiH "the monkeys will hate the two men"

how to choose a tiG that represents the doermmmmmmmmm ^ C- 1702

Find the person of the doer of the root. That means: if the doer includes me, we need a first person affix, if the doer includes you but not me, we need a second person affix, otherwise we need a third person affix.

Find the number of the doer. Can be singular, dual or plural.

Now we take the affixes in the tiG list that have the same person and number as our doer. There are two of them, one flat and one bent.

We use the flat unless any rule tells us that we have to use the bent.

Examples --

"they cook" and "they jump" and "they sit" will all need a third person plural affix.

There are two such affixes: jhi is flat and jha is bent.

Most roots, such as pac, get the flat --

pac + laT → pac + jhi → pac + zap + jhi →jhontaH pac + zap + anti →atoguNe pacanti

Root plu however gets the bent affix, because rule anudAttaGi says so --

plu + laT → plu + jha → plu + zap + jha →hardsoft plo + zap + jha →ecoya plav + zap + jha →jhontaH plav + zap + anta →Tita plav + a + ante →atoguNe plavante

Root As too always gets bent affixes, because it is flagged with "A." in dictionaries --

As + laT → As + jha →AtmanepadeSvanataH As + ata →Tita Asate

how to choose a tiG that does not represent the doermmmmmmmmm ^ C- 1703

If the root is objectful, we must choose the bent tiG that has the same number and person as the object of the root, not the doer.

If the root is objectless, we always choose ta.

Examples --

When anyone cooks a chicken, the object (the chicken) is third person and singular and we need to use the bent affix ta.

pac + laT → pac + ta → pac + yak + ta →Tita pacyate "it is being cooked "

as in --

pacyate kukkuTI "hen is being cooked"

pacyate kukkuTI mayA "I cook hen"

When plu means "jump over something" it is objectful. If the something is mountains, we need the bent third person plural affix, namely jha --

plu + laT → plu + jha → plu + yak + jha →jhontaH plu + yak + jhe →akRtsArva plU + yak + ta → plU + yak + te''' →atoguNe plUyante "they are being jumped over"

as in

plUyate girayo hanumatA "mountains are jumped over by hanumAn, hanumAn jumps over mountains"

Examples with objectless roots --

If plu is objectless --

plu + laT → plu + ta plUyate "jumping is ongoing"

as in

plUyate kapibhiH "monkeys jump"

As is always objectless --

As + laT → plu + ta Asyate "sitting is ongoing"

as in

Asyate mayA "I'm sitting"

inria reader verb cheatsheetmmmmmmmmm ^ C- 1706

tenses --

pr. = laT

impft. = laG

imp. = loT

opt. = hard liG

ben. = soft liG

pft. = liT

fut. = lRT

per. fut. = luT

aor. = luG

numbers --

sg. = singular

du. = dual

pl. = plural

persons --

3 = third person

2 = second person

1 = first person

pada --

ac. = flat ending

mo. = bent ending

ps. = bent ending after yak

Example. Type adveSam into inria reader, set KH, and click the red adveSam box. You will see this --

dviS_1 impft. [2] ac. sg. 1

Here --

* dviS_1 is the root. Clicking it, you should get to the dictionary, where it explains that dviS means to hate.

* "impft" means that the tense is laG.

* The [2] means that the rule [2] in page verb classes worked, because dviS is a class two root before a doer affix.

* "ac" means that the ending is flat, and

* "sg 1" means that the tiG affix is singular first person, so it is mip.

Therefore inria is telling us that --

dviS + laG → dviS + mip →adipra dviS + mip adveSam

At this point we can say that adveSam means "I hated", that rule adipra worked, and that some rules changed dviS into adveS and mip into am.

how to use inria reader to disassemble verbsmmmmmmmmm ^ C- 1707

Write this into inria reader --

admi nayati adanti Adan adveSam

and set KH and press the "read" button.

The red boxes show the analyses of the words that might be verbs. For instance, click the red box "admi". It will show --

[ad_1] pr. [2] ac. sg. 1 X

The ad_1 between brackets is the root. pr is the tense, namely laT, and the ac sg 1 thing tells us that laT was replaced with the flat singular first person tiG affix, namely with mip. So inria is telling us that the verb admi is built this way --

ad + laT → ad + mip admi

Similarly, clicking the red box adveSam inria shows --

[dviS_1] impft [2] ac sg 1 X

Which means that the root is dviS, the tense is laG, and was replaced with mip . Therefore --

dviS + laG → dviS + mip adveSam

We can see that dviS became adveS and mi became am, but unfortunately inria does not tell us which rules did these changes. Yet, knowing the meaning of the root, the tense and the mip, that's enough for us to figure out that adveSam means "I hated".

So before worrying about learning rules, we need to learn the meanings of the inria abbreviations.

See also examples of using inria to disassemble verbs .

building admimmmmmmmmm ^ C- 1711

how to build admi using the rules

how to build admi using inria conjugation

how to build admi using hyderabad

how to build admi using the rulesmmmmmmmmm ^ C- 1712

One way of building a verb that means "I am eating" is using the pANini rules --

(1) choose a root that carries the meaning of "eating", like ad (there are many others, like bhuj, khAd, gras, carv).

(2) add to it the tense laT, which, according to rule vartamAne laT, may be used to express that the action of eating is happening now.

(3) apply rule lasya and replace the laT with the affix mip, which, according to several rules, may be used to express that the doer of the action of eating is singular and first person. In less words, that the doer is "I". We know that mip is first person because rule tiGas trINi trINi says so, and we know that it is singular because of rule tAnyeka.

So far we have --

ad + laT →lasya ad + mip

Now, mip is hard and expresses the doer of the action of the root, as it says who is eating. So we might think that kartarizap should work. However, it doesn't, because of the exception adi-prabhRtibhyaH zapaH, which says that after some roots, such as ad, rule kartarizap does not work and the root gets no affix.

As it happens, no other rules can apply at this point. So we are already done, and all that we have to do to get our verb is removing the label letter p (we know that p is a label because rule halantyam says so). So we have --

ad + laT →lasya ad + mip → admi "I eat"

(as rule lasya works every single time we build a verb, I will write this, for short --

ad + laT mip → admi "I eat"

this " ad + laT mip" means that we add laT after ad and then replace the laT with mip. It does NOT mean that we first add laT and then we add mip.)

Now, if you try to build a verb in this way you will fail horribly, because to do this, you need to know all the rules. Otherwise, you don't know even WHEN to stop. We apply changes as long as some rule says we must, and we are done only when no more rules apply.

So even though using pANini rules to build verbs is what "we are supposed to learn eventually", beginners will not be able to do this for a long time. Meanwhile students are supposed to use shortcuts, like asking the teacher "how do you say I'm listening?". Since the 20th century we can use inria tools and hyderabad tools to build verbs, and maybe at some point in the 21th century the AI chatbots will learn to do that.

how to build admi using hyderabadmmmmmmmmm ^ C- 1714

The hyderabad tools are more accurate than the inria tools, but quite more inconvenient for the average European or American student. The problem is that as they have been made in an Indian university, they take for granted that you can read devanAgarI fluently. That is a very reasonably assumption to make if your students are all in India.

But MY students are mostly outside India and are the kind of lazy folks that won't learn devanAgarI until the last possible moment, so I tell them to compensate for their illiteracy by using a transliterator gadget, such as this one.

So how do we get admi out of the hyderabad tools?

Go to the hyderabad tools page and choose "verb forms generator" from the menu. In the gadget, choose your alphabet, your root, and parasmaipada (parasmaipada because you want the flat affixes, ac). Choose the output alphabet, and click "generate". You get to a table that shows all the tenses. The present is laT.

The verb tables in hyderabad are written in the Indian order: third person affixes go at the top, second person in the middle and first person are last. So here for "I eat" you need the form that is at the bottom left of the laT table.

building adantimmmmmmmmm ^ C- 1716

The rules that build adanti "they eat" are these --

ad + laT → ad + jhi →jhontaH ad + anti → adanti "they eat"

Rule jhontaH (literally, "jh to ant") replaces the jh of all affixes that have jh with ant. In this example, it changed the jh part of jhi into ant, and the i of jhi stayed unchanged, so we got anti. This same rule will change jha into anta, jhu into antu and so on. It works only on the jh that is inside an affix.

This rule will work on nearly all jhi, excepting only the ones that come after zlu and the ones that come after one the seven jakSi roots. In those cases, jhontaH does not work, because its exception adabhyastAt turns jhi into ati.

analyzing carantimmmmmmmmm ^ C- 1719

caranti means they move, and this word is made by adding the plural affix jhi. Inria says --

car pr. [1] ac pl 3

the "ac pl 3" (plural third person) means that we added jhi.

car + laT

car + jhi

the [1] means that kartarizap worked, so zap was added after the root, and inria is saying that --

car + zap + jhi → cara + jhi caranti

Apparently, jhi turned into nti by some special rules.

analyzing nayatimmmmmmmmm ^ C- 1721

Writing nayati into inria reader , it gives us two options, one red and one blue. That's because this word can be a noun or a verb. We are interested only in the verb, so we click the red. Doing this shows --

nI_1 pr [1] ac sg 3

The [1] there means that the rule [1] of the table verb classes worked and added the affix zap after the root. The root nI means to carry or lead, so, so far, we can say that nayati means "leads", and was built like this --

nI + laT tip → nI + zap + tip nayati "he leads"

as in

senAnM nayati zalyo 'yam "this zalya leads the army"

or

grAmaGM kRSNo nayaty ajAM "K. leads the goat to the village"

It's clear that some rule or rules turned nI + zap into naya. We'll see those in a moment.

building nayatimmmmmmmmm ^ C- 1722

The rules that build nayati are these --

nI + laT tip →kartarizap nI + zap + tip →hardsoft ne + a + ti →ecoyavAyAvaH nayati "he leads"

Rule kartarizap teaches: "whenever a root is right in front of a hard affix that means the doer, add the affix (z)a(p) after the root".

In this example, kartarizap works because

(1) tip is hard, because rule tiGzit says so.

(2) tip means the doer, because it expresses that the doer is third person and singular (he or she does the leading, not you or me)

(3) None of the dozen plus exception rules that stop kartarizap from working applies in this example. We'll worry about those rules later. For now, just remember that the class one roots (nI, car, plu and all the roots that inria labels sometimes with a [1]) get zap, and roots of classes two to nine never do.

Here you have some more examples of the root nI getting zap --

nI + laT sip → nI + zap + sip nayasi "you lead"

nI + laG sip → nI + zap + sip anayas "you led"

nI + loT sip → nI + zap + sip naya "lead!"

nI + liG sip → nI + zap + sip nayes "you would lead"

Now, in all these examples, nI plus zap turned into naya. Why? Because of rules hardsoft and ecoya.

Let's go back to explaining nayati. We had reached this point --

nI + laT tip →kartarizap nI + zap + tip

Now, rule hardsoft teaches, among other things,

" I turns into e in front of all root affixes "

In our example, zap is a root affix because it is hard, and it is hard because it has z label (see tiGzit). It also happens that none of the many exceptions to hardsoft prevent it from working in this example. Therefore we must replace the I with e --

nI + laT tip →kartarizap nI + zap + tip →hardsoft ne + a + ti

At this point rule ecoyavAyAvaH must work. This is not a verb building rule, but a letter rule that affects all of the e o ai au that are inside a word and before a vowel. Using it is compulsory. After that, no more rules can apply, so we are done --

nI + laT tip →kartarizap nI + zap + tip →hardsoft ne + a + ti →ecoyavAyAvaH nayati "he leads"

analyzing nayantimmmmmmmmm ^ C- 1723

nayanti shows in inria almost like nayati, the only difference being that nayati has ac sg 3 (namely tip) and nayanti has ac pl 3 (namely jhi). As inria shows [1], zap was added to the root. So nayanti means "they lead", and has jhi affix --

nI + laT jhi →kartarizap nI + zap + jhi nayanti "they lead"

so it looks like some rules changed jhi into nti. We'll see those rules right below.

building nayantimmmmmmmmm ^ C- 1724

The rules that build nayanti "they lead" are these --

nI + laT jhi →kartarizap nI + zap + jhi →jhontaH nI + a + anti →hardsoft ne + a + anti →ecoya naya + anti →atoguNe nayanti "they lead"

The jhi ending is almost always affected by jhontaH and turned into anti.

Here atoguNe is not a verb construction rule, but a sandhi rule (a general rule about letter changes). Ordinarily, two a will combine into one long A by rule akassa. But when the two a belong to the same word, like here, they make a short a, by exception atoguNe.

analyzing dveSmimmmmmmmmm ^ C- 1725

Inria shows --

dveSmi = dviS pr [2] ac sg 1

which means

dviS + laT mip → dviS + mi dveSmi "I hate"

The [2] means that rule adipra worked, so no affix (such as zap) was added after dviS.

As we were expecting dviSmi, this means that some rule changed dviS into dveS.

building dveSmimmmmmmmmm ^ C- 1726

The rule that changed diS into dveS was puganta. This rule, among other things, teaches --

"replace the nexttolast i of a root with e before all root affixes"

Here no exception prevents puganta from working, so we say --

dviS + laT mip → dviS + mi →puganta dveSmi "I hate"

analyzing cakArammmmmmmmm ^ C- 1733

According to inria, cakAra is --

kR pft ac sg 3

as " ac sg 3" means tip, here we had

kR + liT tip cakAra "he made"

This is the same thing as !"cakratus above, only that we added tip ( singular third person) instead of tas ( dual third person). Here kR turned into cakAr before tip, not into cakR, and tip turned into a. Again inria did not show a verb class.

building cakArammmmmmmmm ^ C- 1734

There are many rules involved into making cakAra. In a nutshell --

kR + liT tip →parasmaipadAnANNa kR + Nal →acoJNiti kAr + Nal →liTidhA cakAr + Nal → cakAra "he made"

Here rule parasmaipadAnANNa replaces tip with Nal.

As Nal has N label, rule acoJNiti works and replaces R with Ar.

Next, rule liTidhA reduplicates the root kAr into cakAr. Reduplicating kAr works a bit different than earlier --

first ekAcodve turns kAr into kAkAr

then hrasvaH turns the first kA into ka, making kakAr

finally kuhozcuH replaces that ka with ca, and we get cakAr.

Then we add (N)a(l) after cakAr --

cakAr + Nal → cakAra

The N label of Nal made us replace R with Ar, and the l label tells us that cakAra has the accent in the kA.

analyzing bhaveyusmmmmmmmmm ^ C- 1735

Typing bhaveyus into inria reader, we get --

bhU_1 opt [1] ac pl 3

An opt in inria means that the tense affix added was liG AND that rule liGAziSi was not applied, so the tiG that replaces the liG is hard. The [1] means that bhU is a zapclass root and rule kartarizap added zap here. So inria is telling us that the verb was formed this way --

bhU + liG → bhU + hard jhi → bhU + zap + jhi bhaveyus "they would be"

The student will remember that bhU before zap turns into bhav by hardsoft and ecoya, so we should have bhavajhi so far. Looks like some rules must be changing ajhi into eyus.

building bhaveyusmmmmmmmmm ^ C- 1736

When we must join a root and a liG replacer affix, like here --

bhU + liG → bhU + hard jhi

there are between fifteen or twenty rules that must work, I lost count. So I will mention here only a few of them.

First, rules kartarizap, hardsoft and ecoya turn bhU into bhava --

bhU + jhi →kartarizap bhU + a + jhi →hardsoft bho + a + jhi →ecoya bhava + jhi

Then rule jherjus works --

bhava + jhi →jherjus bhava + (j)us

Now, usually, when a flat affix replaces liG, rule yAsuTp should work and add yAs in front of that affix. However, when the affix is right after an a, like here after bhava, exception atoyeya says that the affix gets Iys instead of the usual yAs --

bhava + us →atoyeya bhava + Iysus

Now the first s disappears by liGassa,

bhava + Iysus →liGassa bhava + Iyus

and the a and the I merge into e by the general rule AdguNaH --

bhava + Iyus →AdguNaH bhaveyus

Putting everything together --

bhU + liG jhi →kartarizap bhU + zap + jhi → bhava + jhi →jherjus bhava + us →yAsuTpa bhava + yAsus →atoyeyaH bhava + Iysus →liGassa bhava + Iyus →AdguNaH bhaveyus "they would be"

building acaratmmmmmmmmm ^ C- 1739

To form acarat using inria, go to inria grammar, and under conjugation write car, set dropdown to KH, set present class to 1, and hit Send. In the resulting table the second paragraph says "imperfect", that's the laG. At the left side of that you have the active, that is the ac endings. Look at the third line for the third person. The sngular is acarat.

To form acarat using the rules, do this --

car + laG tip → acar + tip → acar + zap + tip →itazca acar + a + t → acarat

Rule itazca tells us that when tip, jhi, sip have replaced a Git tense, they lose their i.

building dRzyatemmmmmmmmm ^ C- 1743

When we want to make a verb that means that one thing is being seen now, we do this --

dRz + laT ta

Here we must use either ta or tip to mean that the object of the root (the thing that is seen) is third person and singular, and only ta and tip are third person and singular. Here, we must use ta because rule bhAvakarmaNoH says that when the affix does not mean the doer it must be bent. So ta is now an affix that means the object.

Being hard affix that does not mean the doer, this ta makes makes rule sArvadhAtukeyak work

dRz + ta →sArvadhAtukeyak dRz + yak + ta

and as ta is a bent affix that replace a T tense ( laT), rule Tita must work --

dRz + yak + ta → dRz + yak + te'''

Putting everything together --

dRz + laT ta → dRz + yak + ta →Tita dRz + yak + te → dRzyate "it is being seen"

This verb can also be translated as "it is seen", but i added the "being" word because in English "it is seen" may mean either present time or past time, while in Sanskrit you use laT for present time and kta or laG or liT or luG for past time --

dRz + kta →vrazca;bhrasja dRSta →STunA dRSTa- "it was seen"

dRz + laG ta →luGlaG adRz + ta → adRz + yak + ta → adRzyata "it was seen"

dRz + liT ta → dRz + ez →liTidhA dRdRz + e →urat dadRze "it was seen"

dRz + luG ta → dRz + cli + ta → dRz + ciN + ta →luGlaG adarz + i + ta →puganta adarz + i + ta →ciNoluk adarzi "it was seen"

example sentences --

candro dRzyate "the moon is being seen"

pratimAsaJM candro dRzyate pUrNimAyAm "the moon is seen every month in the fifteenth night"

candro dRSTaH "the moon was seen"

candro 'dRzyata "the moon was seen"

candro dadRze "the moon was seen"

candro 'darzi "the moon was seen"