It is handy to have a structured way to summarize and present analogies. We'll use the following conventions for doing this. A mapping will be displayed in terms of three tables:
An example will make this clearer. Consider the following description of a simple water flow:
(cause (> (pressure beaker) (pressure vial))
(flow beaker vial water pipe))
(> (diameter beaker) (diameter vial))
(clear beaker)
(flat-top water)
(liquid water)
A very simple description of heat flow is:
(flow coffee ice-cube heat bar)
(> (temperature coffee) (temperature bar))
(flat-top coffee)
(liquid coffee)
(Notice that these descriptions are slightly more complicated than we used in class.) Feeding these descriptions into SME, with simple water flow as the base and simple heat flow as the target, yields two mappings. Here is how they look given the conventions above:
Mapping 1
Entity correspondences:
| pipe | bar |
| water | heat |
| beaker | coffee |
| vial | ice cube |
Expression correspondences:
| (flow beaker vial water pipe) | (flow coffee ice-cube heat bar) |
| (> (pressure beaker) (pressure vial)) | (> (temperature coffee) (temperature ice-cube)) |
Candidate inferences:
| (cause (> (temperature coffee) (temperature ice-cube)) (flow coffee ice-cube heat bar)) |
| (liquid heat) |
| (flat-top heat) |
| (clear coffee) |
| (> (diameter coffee) (diameter ice-cube)) |
Mapping 2
Entity correspondences:
| beaker | coffee |
| vial | ice cube |
Expression correspondences:
| (> (diameter beaker) (diameter vial)) | (> (temperature coffee) (temperature ice-cube)) |
Candidate inferences:
| (cause (> (pressure coffee) (pressure
ice-cube)) (flow coffee ice-cube (skolem heat) (sketching bar))) |
| (clear coffee) |
A few observations about this method of working through an analogy:
Last edited 10/31/02, by KDF.