The Evolution
14
"blade" to restrict what may be yielded to a concept from the class of
blades; "hospital" then selects from this class a particular form of
"blade," perhaps "scalpel." Thus, unlike in a Type I intersection, the
parts of a Type II intersection perform in different roles.
The Type III intersection, in contrast to all of the above, involves
two parts neither of which restricts. In other words, in yielding
"orange juice," neither "Florida" nor "eggs" is contained within "orange
juice." The "Florida eggs" intersection of "eggs" is interesting in
that it involves two concepts intersecting a third concept. Good examples
of this type of intersection are difficult to find as two concepts
usually either single out a large number of intersected concepts, or
no intersected concepts. Much easier to find are Type III intersections
in which two concepts intersect an ambiguous word, as, for instance, the
concepts "computer" and "horse" intersect the word bit. In the same way,
"smoke" and "water" intersect pipe; "plaster" and "actors" intersect cast;
"eye" and "student" intersect pupil; "comma" and "stomach" intersect
colon; "month" and "army" intersect March; and "gas" and "army" intersect
tank.
Note that there are three ways to identify the type of an intersection.
The first is by simple inspection, as described above. The second is by
examining what in memory has occurred contiguous with what, and then
deducing from this what types of intersections are possible (this tech-
nique is treated in the section on the requirement of contiguous occurrence).
And the third is by backward inference (this is where one observes how