chunk 80: verb building machine chunk 80: verb building machine→ discarded lessons AND / OR random writings and summaries
verb building machine
analysing
building
How to build verbs when you don't know yet the rules.
analysing
building
analysing
building
analysing
building
analysing
building
analysing
building
analysing
building
analysing
building
analysing
building
analysing
building
analysing
building
analysing
building
building
^ 
Many of the
(1) choose a root and a tense, add the tense after the root
(2) replace the tense with one of the eighteen tiG affixes
(3) let the magic
Examples --
ad + laT →
nI + laT → 
dviS + laG →
kR + liT →
bhU + liG → bhava +
In the first example,
In the second example
In the third example,
In the last example, bhU + jhi, some rules changed bhU into bhava, other rules changed jhi into
In theory, a person that has mastered the grammar and knows all rules can see a verb like
Until we get to that level, we have to cheat. While you're learning, if you have a good teacher, you can ask how to assemble or disassemble a verb. Without a teacher, we can use inria or hyderabad to disassemble and assemble.
In the following pages, I show some examples of how to use inria to disassemble a verb. This machine, most of the time, shows us the root, tense and tiG from which the verb was made, but does not show which grammar rules were used to make it. So I'll show those rules myself in the pages below.
^
Typing
pr means that the tense affix laT was added after the root
ac means that this laT was replaced with a flat affix
sg 1 means singular first person. Therefore the flat affix was mip.
The "[2]" thing means that this root
So
^
One way of building a verb that means "I am eating" is using the rules --
(1) choose a root that carries the meaning of "eating", like
(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 --
At this point a beginner might think that rule kartarizap should apply. This rule says that when a root is right before an affix such as the mip here, which is a hard affix and expresses the doer of the action of the root (it says who is eating), we must add the affix zap right after the root. However, that rule does not work, because of the exception rule adi-prabhRtibhyaH zapaH. This rule says that after some roots, such as ad, dviS and others, rule kartarizap does not work and we add nothing after the root. It happens that no one of the other hundreds of rules that describe verb building works in this case. So we are already done, and all that we have to do to get our verb is removing the
ad + laT →
(as rule lasya works every single time we buikd a verb, I will write this, for short --
when I say ad + laT mip I mean that I add laT and then replace the laT with mip. I do not mean that I first ad d laT and then I add mip after it.)
Now, if you try to build a verb in this way you will fail horribly, because you don't know any of the rules that might or might not apply.
Beginners MUST use the inria conjugation gadget to build their verbs. To see how this works, please read how to build verbs when you don't know yet the rules .
Using the magic gadget, you can figure out that ad + laT tip makes
If you are curious, the rule that worked here was kharica. This rule changes into
(howtobuildverbswhenyou) (howbuilr)
^
Look up
First look carefully at the top line. It says "Conjugation tables of ad_1". The ad_1 is important, because it means that
No, the first paragraph is labeled "present" and it shows the forms that we get when we add laT after ad. In this case we get two tables, "active" and "passive".
The table in the left, "active" shows the ac, that is, those made with the first nine tiG affixes mip vas mas etc.
In that table we have three rows of three words, which show the result of adding the different affixes. In this case we want the first person affix mip, so we look at the first line, that contains the results of adding the three first person affixes mibvasmas. The one that we need is the one on the left,
^
Writing
This means that the tense affix added was the present (a.k.a. laT) and it was replaced with the plural third person flat affix (a.k.a. jhi). So
and it is clear that some rule or rules changed jhi into
Most of the verbs that end in
The true answer to that question is quite long. But for now we can say that the list has jhi because some of the third person plural verbs end in
^
The rules that build
Rule jhontaH (literally, "
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
^
Writing
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
nI + laT tip →
as in
or
It's clear that some rule or rules turned
^
The rules that build
nI + laT tip →
Rule kartarizap teaches: "whenever a root is right in front of a hard affix that means the doer, add the affix
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 (
Here you have some more examples of the root nI getting zap --
nI + laT sip →
nI + laG sip →
nI + loT sip →
nI + liG sip →
Now, in all these examples, nI plus zap turned into
Let's go back to explaining
nI + laT tip →
Now, rule hardsoft teaches, among other things,
"
In our example, zap is a root affix because it is hard, and it is hard because it has
nI + laT tip →
At this point rule ecoyavAyAvaH must work. This is not a verb building rule, but a letter rule that affects all of the
nI + laT tip →
^
so it looks like some rules changed
^
The rules that build
The jhi ending is almost always affected by jhontaH and turned into
Here atoguNe is not a verb construction rule, but a sandhi rule (a general rule about letter changes). Ordinarily, two
(analysingdveSmi) (analysiveSm)
^
Inria shows --
which means
The [2] means that rule adipra worked, so no affix (such as zap) was added after dviS.
As we were expecting
(buildingdveSmi) (buildinveSm)
^
The rule that changed
"replace the nexttolast
Here no exception prevents puganta from working, so we say --
(analysingdviSanti) (analysiS)
^
Inria shows --
which means
there was no change of
^
This time, puganta did not work. Why? Because of the exception kGitica, which teaches, among other things --
" puganta will not work before affixes that have
and it happens that jhi is such an affix.
In fact, jhi is just an abbreviation of
So, how do we know that jhi has
Because rule hard
The smart student will have now figured out that when we have laT after dviS, the dviS will only become
(1) puganta does not work before affixes with
(2) a hard that has no
Therefore, when a hard affix carries BOTH
(analysingadveSam) (analysiveSa)
^
inria reader paints
Here the root is dviS, impft means that laG was added, [2] means that rule adipra worked, and " ac sg 1" is the mip affix,
So, Inria tells us that --
which means "I hated".
Here dviS plus
(buildingadveSam) (buildinveSa)
^
dviS + laG mip →
Incidentally, rule adipra worked and told us that rule kartarizap must not work after ad, dviS and other roots. This is why we did not add zap after the root like we did earlier in
The
"whenever the tense is laG luG or lRG, and the root starts with a consonant, add
(This rule applies to luG laG lRG only.)
Therefore, as
Now. When mip has replaced a Git tense, such as laG or liG or luG, rule tasthas always replaces the affix mip with the affix am'''.
Because of rule sthAnivad, this
(analysingcakratus) (analysir)
^
Type
According to inria,
ac du 3 means the affix tas, so the verb was built this way --
kR + liT tas
Here kR became cakR before a liT affix, tas, and the liT affix tas turned into atus, and the two pieces
Notice that inria did not show a verb class, even though kR belongs to class [8]. That's because the rules mentioned in verb classes never add any affix to the root that is before a liT. Those rules only work before hard affixes, and the affix ( tip, tas, jhi...) that replaces liT is never hard, because rule liTca says so. So the liT verbs are always made the same way no matter the class of the root, and inria does not show the class number because doing that would not help you.
(buildingcakratus) (buildinrat)
^
There are many rules involved into making
kR + liT tas →
The first rule parasmaipadAnANNa replaces tip tas jhi... with Nal atus us... respectively. Here it replaced tas with atus.
The second rule liTidhA says that we must reduplicate most roots when they are before liT. The process of reduplication is quite complicated and it is described in ekAcodve and the rules that follow. In this case it is done in three steps:
ekAcodve turns
urat and another rule turn the first
kuhozcuH replaces that
So far we got --
and now rule ikoyaNaci turns
^
According to inria,
as " ac sg 3" means tip, here we had
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
^
There are many rules involved into making
kR + liT tip →
Here rule parasmaipadAnANNa replaces tip with Nal.
As Nal has
Next, rule liTidhA reduplicates the root
first ekAcodve turns
then hrasvaH turns the first
finally kuhozcuH replaces that
Then we add
The
(analysingbhaveyus) (analysivey)
^
Typing
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
The student will remember that
(buildingbhaveyus) (buildinvey)
^
When we must join a root and a liG replacer affix, like here --
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
Then rule jherjus works --
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
Now the first
and the
Putting everything together --
^
inri reader paints
Here ac sg 3 means tip, an ending that shows
that the doer is third person singular.
and means "he moves" (any kind of movement, such as walking, galloping, swimming, jumping or slithering).
As we were expecting that car + a + ti would make
HOW TO ANALYSE
Hyderabad tools do the same job inria does, but it is more inconvenient, particularly for the student that cannot read devanAgarI yet. The advantage is that it is mor eaccurate -- it gets right some forms that inria gets wrong. so I only use it whne I suspect that inria is failing.
Go to hyderabat toolkit, and in the tools menu , select the morphological analyser. Set input tnecoding to KH, type
Here
car is the root
laG is the tense
so
So this is saying the same thing inria says --
^
To form
To form
Rule itazca tells us that when tip, jhi, sip have replaced a Git tense, they lose their
(analysingplavate) (analysiav)
^
In all the examples we have seen so far, the verb had one of the first nine affixes in list tiptas, and inria said ac to tell us had one of those affixes. When the verb has any of the other nine affixes, inria says either mo or ps. It says ps if yak was added after the root, mo otherwise.
To see an example, type
Here the root is plu, the tense is pr ( laT), and sg 3 means third person singular, like earlier. But here we have mo, not ac. mo and ps mean that one of the bent tiG affixes was added. Of those nine, only the affix ta is third person singular. As we do not have ps here, we know that yak was not added after the root, and as we have [1], we know that zap was added. So inria is saying that --
So, somehow
^
Because of rule anudAtta;Gi, after some roots, we cannot use flat affixes like tip to show who the doer is. Instead, we must use bent affixes like ta. One of these roots is plu "jump, swim, fly", that must take bent only because rule anudAttaGi says so. So to make a verb meaning "he jumps" we start with the jumping root
plu + laT ta →
Here the ta affix means that the doer is singular and third person, same thing that tip means. Being an affix that means the doer, kartarizap must work, and we get hardsoft and ecoya just like we saw earlier in
The Tita rule changed
In some cases we can use the same affix ta to mean that the object of the action is singular third person. In that case, the ta is hard but does not mean the doer, so
The rules that build
plu + laT ta →
(buildingcaranti) (buildinran)
^
the "ac pl 3" (plural third person) means that we added jhi.
the [1] means that kartarizap worked
Now, the special rules. Rule jhontaH says that jhi must be replaced with anti''' most of the time (to be precise, jhi becomes
Now another special rule works: atoguNe. It says that when we have two
Summarizing --
chunk 80: verb building machine