]> 2008/06/10 OpenCyc Knowledge Base Copyright© 2001-2008 Cycorp, Inc., http://www.cyc.com/, Austin, TX, USA This file contains an OWL representation of information contained in the OpenCyc Knowledge Base. The content of this OWL file is licensed under the Creative Commons Attribution 3.0 license whose text can be found at http://creativecommons.org/licenses/by/3.0/legalcode. The content of this OWL file, including the OpenCyc content it represents, constitutes the "Work" referred to in the Creative Commons license. The terms of this license equally apply to, without limitation, renamings and other logically equivalent reformulations of the content of this OWL file (or portions thereof) in any natural or formal language, as well as to derivations of this content or inclusion of it in other ontologies. externalID A unique, language-neutral, variable-sized identifier for a concept that can be used to refer unambiguously to that concept across OWL exports or across Cyc inference engines. label A natural-language representation for a concept that is both human readable and readable by the Cyc inference engine. These terms are not guaranteed to refer to the same concept across time but are guaranteed to be consistent within a particular OWL export. Use 'cycAnnot:externalID' for unambiguously referring to a concept across OWL exports or across Cyc inference engines. EventOrRoleConcept the event or role domain A <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4ret7qgOKgEdmAAAACs6hfSg" class="cyc_term">ConceptTypeByDomain</a> (q.v.). Instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r8IAy8P-fEdmAAAACs0uFOQ" class="cyc_term">EventOrRoleConcept</a> are collections and relations having to do with general kinds of events and the roles that things can play in them. Major specializations of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAA5wpEbGdrcN5Y29ycA" class="cyc_term">Role</a>, and other relations used for stating significant facts about events (such as time, place, causes, and effects) are instances of this collection. event or role concepts event or role concept

pre-existing actor preActors An <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAKZwpEbGdrcN5Y29ycA" class="cyc_term">ActorSlot</a> (q.v.) that relates an event to those of its participants that pre-exist it. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWDKWZwpEbGdrcN5Y29ycA" class="cyc_term">preActors</a> EVENT OBJECT)</code> means that <code>OBJECT</code> is a participant (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjFpZwpEbGdrcN5Y29ycA" class="cyc_term">actors</a>) in <code>EVENT</code> and that <code>OBJECT</code> exists before <code>EVENT</code> begins. Note that <code>OBJECT</code> also exists during at least part of <code>EVENT</code> (as <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjFpZwpEbGdrcN5Y29ycA" class="cyc_term">actors</a> generalizes to <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjIm5wpEbGdrcN5Y29ycA" class="cyc_term">temporallyIntersects</a>). <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWDKWZwpEbGdrcN5Y29ycA" class="cyc_term">preActors</a> is a very general actor-slot, subsuming <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1HmJwpEbGdrcN5Y29ycA" class="cyc_term">doneBy</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi65pwpEbGdrcN5Y29ycA" class="cyc_term">objectActedOn</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a>, and many others.

PhysicalContactEvent event involving physical contact A collection of physical events in which two or more objects are in physical contact (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkFaJwpEbGdrcN5Y29ycA" class="cyc_term">touches</a>) for at least part of the event's duration. Note that, although most <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjpjZwpEbGdrcN5Y29ycA" class="cyc_term">PhysicalEvent</a>s involve some kind of touching, only those for which contact is salient should be instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjnQpwpEbGdrcN5Y29ycA" class="cyc_term">PhysicalContactEvent</a>. For events involving continuous contact and events in which contact is made, respectively, see the specializations <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvv2wdZwpEbGdrcN5Y29ycA" class="cyc_term">ContinuousPhysicalContactEvent</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwQTcupwpEbGdrcN5Y29ycA" class="cyc_term">PhysicalContactMakingEvent</a>.

A predicate for relating a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViexZwpEbGdrcN5Y29ycA" class="cyc_term">Communicating</a> event to an agent participating in the event. (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwRRi2pwpEbGdrcN5Y29ycA" class="cyc_term">communicationParticipants</a> COMM AGENT) means that AGENT is a participant in COMM. communicationParticipants communicator

inputsDestroyed The predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWWNUJwpEbGdrcN5Y29ycA" class="cyc_term">inputsDestroyed</a> is used to relate a particular event to the item or items destroyed in that event. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWWNUJwpEbGdrcN5Y29ycA" class="cyc_term">inputsDestroyed</a> EVENT OBJECT)</code> means that <code>OBJECT</code> exists before <code>EVENT</code>, is affected by <code>EVENT</code>, and due to that involvement, ends its existence at some time during <code>EVENT</code>. Note that <code>OBJECT</code> may or may not be acting deliberately (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1fHJwpEbGdrcN5Y29ycA" class="cyc_term">deliberateActors</a>) in <code>EVENT</code>. thing destroyed

motionPathway-Partial path overlapping the path of motion An <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAKZwpEbGdrcN5Y29ycA" class="cyc_term">ActorSlot</a> and specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv2yvB5wpEbGdrcN5Y29ycA" class="cyc_term">genericPathway_Partial</a> that relates a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOcJwpEbGdrcN5Y29ycA" class="cyc_term">Movement_TranslationEvent</a> to a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwJXokJwpEbGdrcN5Y29ycA" class="cyc_term">Path_Spatial</a> such that at least part of the movement is along part of the path. It can be used to indicate one of the paths followed in a movement event. More formally, <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv_QFmJwpEbGdrcN5Y29ycA" class="cyc_term">motionPathway_Partial</a> MOVE PATH)</code> means that <code>MOVE</code> has a trajectory (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv_YPjpwpEbGdrcN5Y29ycA" class="cyc_term">trajectory_Complete</a>) with a sub-trajectory in common with some <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvioitpwpEbGdrcN5Y29ycA" class="cyc_term">subPaths</a> of <code>PATH</code>. For example, if a certain trip to Dallas from Austin is via highway I-35, this does not imply either that the whole journey is along I-35 (it also may be along driveways and side streets), or that it is along all of I-35 (which would take you from the Mexican border all the way to the Canadian border). A part of the journey is along a part of I-35. Contrast this predicate with <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViCe5wpEbGdrcN5Y29ycA" class="cyc_term">motionPathway_Complete</a>, which relates a movement event to a spatial path followed throughout all of the movement.

Movement-TranslationProcess A subcollection of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOcJwpEbGdrcN5Y29ycA" class="cyc_term">Movement_TranslationEvent</a>s whose instances are, practically speaking, continuous processes. In any instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOL5wpEbGdrcN5Y29ycA" class="cyc_term">Movement_TranslationProcess</a>, all time-slices of that process are also themselves instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOL5wpEbGdrcN5Y29ycA" class="cyc_term">Movement_TranslationProcess</a>. Note that walking is a type of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOL5wpEbGdrcN5Y29ycA" class="cyc_term">Movement_TranslationProcess</a>, even though it involves some nonzero accelerations and jerks. Non-examples include Captain Kirk beaming up to the Enterprise and the "tunneling" of an electron in a tunnel diode. movement process

cotemporalSubEvents The predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkGvpwpEbGdrcN5Y29ycA" class="cyc_term">cotemporalSubEvents</a> is used to relate an event to some sub-event which has the same duration as the whole event, but doesn't necessarily include everything that happens in the whole event. (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkGvpwpEbGdrcN5Y29ycA" class="cyc_term">cotemporalSubEvents</a> WHOLE PART) means that WHOLE and PART are cotemporal events (i.e., they have the same exact duration), and PART is a component of WHOLE. For example, a particular instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rdp8N1ocJQdicUre0IqdPPg" class="cyc_term">RainStormAsEvent</a> may have distinguishable <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkGvpwpEbGdrcN5Y29ycA" class="cyc_term">cotemporalSubEvents</a> for (1) raining and (2) wind blowing, and an instance of swimming <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP3yxJwpEbGdrcN5Y29ycA" class="cyc_term">Backstroke</a> has separable events for (1) kicking and (2) arm motion throughout the swimming. See also <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjWz5wpEbGdrcN5Y29ycA" class="cyc_term">cotemporal</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViQmZwpEbGdrcN5Y29ycA" class="cyc_term">subEvents</a>. Cotemporal Sub Events

change of device state A specialization of both <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjpjZwpEbGdrcN5Y29ycA" class="cyc_term">PhysicalEvent</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWESd5wpEbGdrcN5Y29ycA" class="cyc_term">IntrinsicStateChangeEvent</a> (q.v.). The collection of events in which a device goes from one basic state (the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWI7B5wpEbGdrcN5Y29ycA" class="cyc_term">fromState</a>) to another (the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWRgjZwpEbGdrcN5Y29ycA" class="cyc_term">toState</a>). A change of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rEJkpOHSyEdaAAACgyZzFrg" class="cyc_term">DeviceTypeByState</a> (q.v.) might be due to an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAB5wpEbGdrcN5Y29ycA" class="cyc_term">Agent_PartiallyTangible</a> adjusting the device, or it might happen automatically due to the behavior of the device itself. The two most general state changes (for powered devices) are from <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rKqORBnS8EdaAAACgyZzFrg" class="cyc_term">Device_On</a> to <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r19FsDHS5EdaAAACgyZzFrg" class="cyc_term">Device_Off</a>, and vice versa. Many other states peculiar to specific devices can be identified. For example, the states of a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjJdZwpEbGdrcN5Y29ycA" class="cyc_term">Dishwasher</a> include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rD3GsoHS9EdaAAACgyZzFrg" class="cyc_term">DeviceState_Washing</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r7_CVUnS9EdaAAACgyZzFrg" class="cyc_term">DeviceState_Rinsing</a>; and the states of a trapping device might include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4roIF4nnS7EdaAAACgyZzFrg" class="cyc_term">TrapArmed</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3EmGdHS6EdaAAACgyZzFrg" class="cyc_term">TrapTripped</a>, and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r2C78vnS-EdaAAACgyZzFrg" class="cyc_term">TrapIdle</a>. Specializations of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjRLZwpEbGdrcN5Y29ycA" class="cyc_term">ChangingDeviceState</a> include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkLWpwpEbGdrcN5Y29ycA" class="cyc_term">UnlockingALock</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rMbLuNA_AQdeX8syxx8Pr6Q" class="cyc_term">ChargingABattery</a>, and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjkXZwpEbGdrcN5Y29ycA" class="cyc_term">ComputerCrashing</a>. ChangingDeviceState

A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOtpwpEbGdrcN5Y29ycA" class="cyc_term">GeneralizedTransfer</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVifB5wpEbGdrcN5Y29ycA" class="cyc_term">InformationTransferEvent</a> is an event in which information is transferred from a source (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV5PA5wpEbGdrcN5Y29ycA" class="cyc_term">informationOrigin</a>) to one or more destinations (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVipxZwpEbGdrcN5Y29ycA" class="cyc_term">informationDestination</a>), where the source and the various destinations are either intelligent agents or <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvkNufpwpEbGdrcN5Y29ycA" class="cyc_term">InformationBearingThing</a>s (IBTs). Examples include reading a book (transfer of information from the book to the reader), saying something to someone (transfer of information from the speaker to the listener), machine translation (transfer of information from an encoded IBT in the source language to an encoded IBT in the target language), OCR scanning (transfer of information from a visual information source to another IBT in a different format), carving initials in a tree (transfer of information from an agent to an IBT), and making a speech (transfer of information from an agent to other agents). See also the specialization <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvucXhJwpEbGdrcN5Y29ycA" class="cyc_term">InformationTransferPhysicalEvent</a>. InformationTransferEvent information transfer

A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVieP5wpEbGdrcN5Y29ycA" class="cyc_term">PurposefulAction</a> and characterized by one or more <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVifB5wpEbGdrcN5Y29ycA" class="cyc_term">InformationTransferEvent</a> sub-events. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViexZwpEbGdrcN5Y29ycA" class="cyc_term">Communicating</a> is an event in which the transfer of information between or among agents is a focal action; communicating is the main purpose and/or goal in the event. That may be contrasted with events which involve communication but wherein the focus is different, e.g., playing cards (wherein the progressive actions -- and winning -- of the game are focal). Since <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViexZwpEbGdrcN5Y29ycA" class="cyc_term">Communicating</a> is a specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVieP5wpEbGdrcN5Y29ycA" class="cyc_term">PurposefulAction</a>, each <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViexZwpEbGdrcN5Y29ycA" class="cyc_term">Communicating</a> event must be intentional on the part of the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rt4Hz8rsOQdiUO4DMdSL3eA" class="cyc_term">communicatorOfInfo</a>; it may or may not be intentional on the part of the agent playing the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rpBwKLLsPQdiZUP7Z9IOkww" class="cyc_term">infoCommunicatedTo</a> role. Hence, a speaker on a soapbox haranguing an indifferent crowd is performing an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViexZwpEbGdrcN5Y29ycA" class="cyc_term">Communicating</a>. In contrast, Juliet soliloquizing on her balcony, unaware that Romeo is listening to her, is not <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViexZwpEbGdrcN5Y29ycA" class="cyc_term">Communicating</a>; rather Romeo (and Juliet, unaware) are engaged in an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWU4VpwpEbGdrcN5Y29ycA" class="cyc_term">Eavesdropping</a>. Communicating may be either a one-way or a two-way transfer of information (cf. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVieg5wpEbGdrcN5Y29ycA" class="cyc_term">CommunicationAct_Single</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViRxJwpEbGdrcN5Y29ycA" class="cyc_term">MultiDirectionalCommunication</a>). Every event belonging to <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViexZwpEbGdrcN5Y29ycA" class="cyc_term">Communicating</a> contains at least one transfer of information between at least two agents who participate in the event. (Note that the latter requirement excludes reading and writing from <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViexZwpEbGdrcN5Y29ycA" class="cyc_term">Communicating</a>, when those events are just the private accessing or generating of information.) Communicating may be specialized in various ways, such as, by the method or medium used (e.g., <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjJB5wpEbGdrcN5Y29ycA" class="cyc_term">AudioCommunicating</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViPa5wpEbGdrcN5Y29ycA" class="cyc_term">NonVerbalCommunicating</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViSEJwpEbGdrcN5Y29ycA" class="cyc_term">FaceToFacePresenceCommunicating</a>); by the type of information involved (e.g., <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVihhJwpEbGdrcN5Y29ycA" class="cyc_term">MakingAnAgreement</a>); by the purpose of the communication (e.g., <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVix4JwpEbGdrcN5Y29ycA" class="cyc_term">Teaching</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjt_5wpEbGdrcN5Y29ycA" class="cyc_term">Negotiating</a>); by the agents involved (e.g., <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj_IJwpEbGdrcN5Y29ycA" class="cyc_term">IntraOrganizationCommunication</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjM8pwpEbGdrcN5Y29ycA" class="cyc_term">StageProduction</a>). Examples of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViexZwpEbGdrcN5Y29ycA" class="cyc_term">Communicating</a> include a symphony performance, an email message, a telephone call, a speech, a handshake, issuing a traffic ticket -- all of which normally, and focally, involve communication between two or more agents. communication Communicating

HumanActivity human activity A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViNqpwpEbGdrcN5Y29ycA" class="cyc_term">AnimalActivity</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViN65wpEbGdrcN5Y29ycA" class="cyc_term">HumanActivity</a> is a spatially-localized action each of whose "doers" (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1HmJwpEbGdrcN5Y29ycA" class="cyc_term">doneBy</a>) is either a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rIcwFloGUQdeMlsOWYLFB2w" class="cyc_term">HomoSapiens</a> or a group of humans (i.e. a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjmoJwpEbGdrcN5Y29ycA" class="cyc_term">Group</a> all of whose members are <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rIcwFloGUQdeMlsOWYLFB2w" class="cyc_term">HomoSapiens</a> or groups of humans).

A specialization of both <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVioQZwpEbGdrcN5Y29ycA" class="cyc_term">Action</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViGFZwpEbGdrcN5Y29ycA" class="cyc_term">AtLeastPartiallyMentalEvent</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVieP5wpEbGdrcN5Y29ycA" class="cyc_term">PurposefulAction</a> is an action consciously, volitionally, and purposefully done by (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVipYpwpEbGdrcN5Y29ycA" class="cyc_term">performedBy</a>) at least one actor. intentional action PurposefulAction

deliberate actor deliberateActors <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1fHJwpEbGdrcN5Y29ycA" class="cyc_term">deliberateActors</a> ACT ACTOR)</code> means that the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAB5wpEbGdrcN5Y29ycA" class="cyc_term">Agent_PartiallyTangible</a> <code>ACTOR</code> is conscious, volitional, and purposeful in the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a> <code>ACT</code>. <code>ACTOR</code> is aware of acting in <code>ACT</code>, and chooses to play the role he/she/it does in <code>ACT</code>.

instrument instrument-Generic The predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV1Os5wpEbGdrcN5Y29ycA" class="cyc_term">instrument_Generic</a> is used to link a particular event to any of the objects which play an instrumental role in it. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV1Os5wpEbGdrcN5Y29ycA" class="cyc_term">instrument_Generic</a> EVENT OBJECT)</code> means that the instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj27ZwpEbGdrcN5Y29ycA" class="cyc_term">PartiallyTangible</a> <code>OBJECT</code> plays an intermediate causal role in the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a> <code>EVENT</code>, facilitating the occurrence of <code>EVENT</code>, and thereby serving some purpose of some <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAB5wpEbGdrcN5Y29ycA" class="cyc_term">Agent_PartiallyTangible</a>. This can happen in at least two ways: either the 'doer' of <code>EVENT</code> acts on <code>OBJECT</code>, which in turn acts on something else (as when someone uses a hammer to pound in a nail) or the 'doer' of <code>EVENT</code> acts on something, making it possible for <code>OBJECT</code> to act on that thing (as when someone puts wet clothes out in the sun to dry). Typically, an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV1Os5wpEbGdrcN5Y29ycA" class="cyc_term">instrument_Generic</a> is not significantly altered by playing that role in an event. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV0FMZwpEbGdrcN5Y29ycA" class="cyc_term">deviceUsed</a> is an important specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV1Os5wpEbGdrcN5Y29ycA" class="cyc_term">instrument_Generic</a> (where <code>OBJECT</code> is an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjHL5wpEbGdrcN5Y29ycA" class="cyc_term">PhysicalDevice</a>).

A binary predicate which relates instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVifB5wpEbGdrcN5Y29ycA" class="cyc_term">InformationTransferEvent</a> to instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvsaaeJwpEbGdrcN5Y29ycA" class="cyc_term">Agent_Generic</a>. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVqYY5wpEbGdrcN5Y29ycA" class="cyc_term">recipientOfInfo</a> TRANSFER RECIP)</code> means that the information transferred in the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVifB5wpEbGdrcN5Y29ycA" class="cyc_term">InformationTransferEvent</a> <code>TRANSFER</code> is received by the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvsaaeJwpEbGdrcN5Y29ycA" class="cyc_term">Agent_Generic</a> <code>RECIP</code>. After <code>TRANSFER</code>, <code>RECIP</code> understands or conceives of the information transferred in <code>TRANSFER</code>; Cyc does NOT conclude that s/he <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkLtpwpEbGdrcN5Y29ycA" class="cyc_term">knows</a> the information or counts it among his/her <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViA0pwpEbGdrcN5Y29ycA" class="cyc_term">beliefs</a>, because <code>RECIP</code> might not believe it. In receiving the information transferred, <code>RECIP</code> may be acting intentionally or unintentionally. Note that if the communication event used in the first argument slot of this predicate is a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVieg5wpEbGdrcN5Y29ycA" class="cyc_term">CommunicationAct_Single</a> and the recipient of the information was intended to receive the information by the originator of the communication event (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVwuhZwpEbGdrcN5Y29ycA" class="cyc_term">communicationTarget</a>) then <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv7XiW5wpEbGdrcN5Y29ycA" class="cyc_term">recipientOfInfo_Intended</a> should probably be used instead of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVqYY5wpEbGdrcN5Y29ycA" class="cyc_term">recipientOfInfo</a>. See also <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWUq7JwpEbGdrcN5Y29ycA" class="cyc_term">infoTransferred</a>, and the slightly orthogonal <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjggpwpEbGdrcN5Y29ycA" class="cyc_term">intendedAudience</a> (which relates instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvkNufpwpEbGdrcN5Y29ycA" class="cyc_term">InformationBearingThing</a> to instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvsaaeJwpEbGdrcN5Y29ycA" class="cyc_term">Agent_Generic</a>). recipientOfInfo perceiver

This predicate is a generalization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV1Os5wpEbGdrcN5Y29ycA" class="cyc_term">instrument_Generic</a> that relates an event (or other temporal situation) to an individual that plays an instrumental role in it (or in bringing it about). (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvaYRIZwpEbGdrcN5Y29ycA" class="cyc_term">instrumentalRole</a> SIT INSTR) means that INSTR is used (in a broad sense of `used') by the "doer" DOER of SIT in order to "do" (or bring about) SIT. DOER will usually (but not necessarily) be an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvsaaeJwpEbGdrcN5Y29ycA" class="cyc_term">Agent_Generic</a>. If SIT is an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a>, DOER is s/he who (or that which) fills the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1HmJwpEbGdrcN5Y29ycA" class="cyc_term">doneBy</a> actor slot with respect to SIT. If SIT is a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvh5TfJwpEbGdrcN5Y29ycA" class="cyc_term">StaticSituation</a>, DOER is somebody who (or something that) is both a primary <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvzSt55wpEbGdrcN5Y29ycA" class="cyc_term">situationConstituents</a> of SIT and has played a salient causal role in bringing SIT about (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwBv8CZwpEbGdrcN5Y29ycA" class="cyc_term">causalActors</a>). Consider a situation of George W. Bush napping on his cot; whether this is construed as an event or as a static situation, Bush would be its "doer" in the present sense and the cot would be playing an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvaYRIZwpEbGdrcN5Y29ycA" class="cyc_term">instrumentalRole</a>. If SIT is an event and INSTR is partially tangible, use <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV1Os5wpEbGdrcN5Y29ycA" class="cyc_term">instrument_Generic</a> or a specialization thereof. But if SIT is a static situation or INSTR is an intangible individual (such as a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj0P5wpEbGdrcN5Y29ycA" class="cyc_term">CommunicationConvention</a> or a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvq7pm5wpEbGdrcN5Y29ycA" class="cyc_term">Letter_CW</a>), <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvaYRIZwpEbGdrcN5Y29ycA" class="cyc_term">instrumentalRole</a> itself might need to be used. For a type-level version of this predicate, see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvXyb35wpEbGdrcN5Y29ycA" class="cyc_term">instrumentalRole_Type</a>. instrumentalRole Instrumental Role

<code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjX_pwpEbGdrcN5Y29ycA" class="cyc_term">providerOfMotiveForce</a> MOVE OBJ)</code> means that the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj27ZwpEbGdrcN5Y29ycA" class="cyc_term">PartiallyTangible</a> <code>OBJ</code> provides, through its expenditure of energy, a significant fraction of the physical force required to make the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEAZwpEbGdrcN5Y29ycA" class="cyc_term">MovementEvent</a> <code>MOVE</code> happen. For example, if <code>MOVE</code> is an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjpy5wpEbGdrcN5Y29ycA" class="cyc_term">PedalingABicycle</a>, <code>OBJ</code> will be the person who is operating the bike. Another example: if <code>MOVE</code> is a use of a belt sanding tool, then <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjX_pwpEbGdrcN5Y29ycA" class="cyc_term">providerOfMotiveForce</a> will relate <code>MOVE</code> to both the electric sander and the person operating the sander, since both the sander and the operator supply a significant fraction of the force required to make <code>MOVE</code> happen. providerOfMotiveForce provider of physical force

senderOfInfo information sender The predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViPLZwpEbGdrcN5Y29ycA" class="cyc_term">senderOfInfo</a> is used to indicate the sending agent in a particular transfer of information. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViPLZwpEbGdrcN5Y29ycA" class="cyc_term">senderOfInfo</a> TRANSFER SENDER)</code> means that <code>SENDER</code> is an agent who is the source of information transferred in the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVifB5wpEbGdrcN5Y29ycA" class="cyc_term">InformationTransferEvent</a> <code>TRANSFER</code>. At the time of <code>TRANSFER</code> (and typically for some period beforehand), <code>SENDER</code> conceives of the information transferred in <code>TRANSFER</code>. It's not the case that SENDER necessarily knows the 'information' or has it among his/her beliefs (see the predicates <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkLtpwpEbGdrcN5Y29ycA" class="cyc_term">knows</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViA0pwpEbGdrcN5Y29ycA" class="cyc_term">beliefs</a>), because <code>TRANSFER</code> could involve lying (e.g., <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwPzTeJwpEbGdrcN5Y29ycA" class="cyc_term">GeorgeWashington</a>'s telling his father, 'I didn't chop down the cherry tree'). Note that <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViPLZwpEbGdrcN5Y29ycA" class="cyc_term">senderOfInfo</a> TRANSFER SENDER)</code> implies that <code>SENDER</code> performs <code>TRANSFER</code> intentionally, in the sense that there is some other agent (related to <code>TRANSFER</code> via <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVwuhZwpEbGdrcN5Y29ycA" class="cyc_term">communicationTarget</a>) that <code>SENDER</code> is attempting to transfer information to via <code>TRANSFER</code>. Of course, <code>SENDER</code> may or may not be successful in transferring that information to the other agent.

A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOtpwpEbGdrcN5Y29ycA" class="cyc_term">GeneralizedTransfer</a> is an event in which something (tangible or intangible) is transferred from one 'place' to another. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOtpwpEbGdrcN5Y29ycA" class="cyc_term">GeneralizedTransfer</a> includes changes in physical location, in ownership or possession, transfer of information, and propagation of wave phenomena through space. See also the related predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rDbKaOuVmQdeTKaYmT-4jgg" class="cyc_term">transferredThing</a>, and the specializations of this collection. GeneralizedTransfer transfer

participant in situation situationConstituents The most general instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwL4_QpwpEbGdrcN5Y29ycA" class="cyc_term">BinaryRolePredicate</a>; that collection's <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvcxuh5wpEbGdrcN5Y29ycA" class="cyc_term">commonGenlPreds</a>. This predicate relates situations (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvYjIS5wpEbGdrcN5Y29ycA" class="cyc_term">Situation</a>) to the tangible and intangible <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjaApwpEbGdrcN5Y29ycA" class="cyc_term">Individual</a>s involved in those situations. (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvzSt55wpEbGdrcN5Y29ycA" class="cyc_term">situationConstituents</a> SIT INDIVIDUAL) means that INDIVIDUAL is a constituent of, or plays some role in, SIT. The role played by INDIVIDUAL might be almost anything, as long as it's "intrinsic" to SIT. Thus to perform, to be changed in the course of, to be information conveyed in, or to be an abstractum the instantiating of which figures in a given situation is to be a constituent of that situation; but to predict, to be a cause or effect of, or to know about a situation is not sufficient to be a constituent. Arguably, INDIVIDUAL must in part constitute SIT, in the modal sense that SIT (that very situation) would not have occurred or obtained had INDIVIDUAL not played the role it did. An important specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvzSt55wpEbGdrcN5Y29ycA" class="cyc_term">situationConstituents</a> is <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjFpZwpEbGdrcN5Y29ycA" class="cyc_term">actors</a> (q.v.), the most general predicate relating <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a>s to their participants.

to-Generic To-Generic <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwAyrYZwpEbGdrcN5Y29ycA" class="cyc_term">to_Generic</a> GEN-TRANS THING)</code> means that the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOtpwpEbGdrcN5Y29ycA" class="cyc_term">GeneralizedTransfer</a> <code>GEN-TRANS</code> has a destination or endpoint <code>THING</code>. Because <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOtpwpEbGdrcN5Y29ycA" class="cyc_term">GeneralizedTransfer</a> covers many kinds of transfer, both physical and abstract, this endpoint can be of many types. In a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv4GokJwpEbGdrcN5Y29ycA" class="cyc_term">Translocation</a> it is a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj27ZwpEbGdrcN5Y29ycA" class="cyc_term">PartiallyTangible</a> location (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjXepwpEbGdrcN5Y29ycA" class="cyc_term">toLocation</a>), while in <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViM85wpEbGdrcN5Y29ycA" class="cyc_term">TransferringPossession</a> it is an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvsaaeJwpEbGdrcN5Y29ycA" class="cyc_term">Agent_Generic</a> (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVipeZwpEbGdrcN5Y29ycA" class="cyc_term">toPossessor</a>). <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwAyrYZwpEbGdrcN5Y29ycA" class="cyc_term">to_Generic</a> encompasses all kinds of endpoints; as a rule, it is better to use more the specific predicates when possible.

output created An <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAKZwpEbGdrcN5Y29ycA" class="cyc_term">ActorSlot</a> that relates <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjeiZwpEbGdrcN5Y29ycA" class="cyc_term">CreationEvent</a>s to things -- tangible objects or other "enduring" things (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi255wpEbGdrcN5Y29ycA" class="cyc_term">SomethingExisting</a>) -- created by those events. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWStbZwpEbGdrcN5Y29ycA" class="cyc_term">outputsCreated</a> EVENT OBJECT)</code> means that <code>OBJECT</code> doesn't exist before <code>EVENT</code> but comes into existence sometime during <code>EVENT</code>, as a result of <code>EVENT</code>. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWStbZwpEbGdrcN5Y29ycA" class="cyc_term">outputsCreated</a> is a specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV5E85wpEbGdrcN5Y29ycA" class="cyc_term">nonDeliberateActors</a>, since it would in general be impossible for <code>OBJECT</code> to act deliberately in its own creation. outputsCreated

moving A specialization of both <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwOf2ypwpEbGdrcN5Y29ycA" class="cyc_term">ActionOnObject</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOcJwpEbGdrcN5Y29ycA" class="cyc_term">Movement_TranslationEvent</a>. In each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjYRJwpEbGdrcN5Y29ycA" class="cyc_term">CausingAnotherObjectsTranslationalMotion</a>, one object causes another object to undergo a translational motion. The object causing the motion is related to the event by <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjX_pwpEbGdrcN5Y29ycA" class="cyc_term">providerOfMotiveForce</a> (q.v.), while the object which is caused to move is related by <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi65pwpEbGdrcN5Y29ycA" class="cyc_term">objectActedOn</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a> (qq.v.). One way to cause another object's motion is to carry it along with oneself (see the specialization <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViMIpwpEbGdrcN5Y29ycA" class="cyc_term">CarryingWhileLocomoting</a>); other ways include throwing it, kicking it, or knocking it away. Some instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjYRJwpEbGdrcN5Y29ycA" class="cyc_term">CausingAnotherObjectsTranslationalMotion</a> may also be instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWH3qpwpEbGdrcN5Y29ycA" class="cyc_term">Translation_Complete</a> (such as instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViMIpwpEbGdrcN5Y29ycA" class="cyc_term">CarryingWhileLocomoting</a>), whereas others (such as instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwPRtTJwpEbGdrcN5Y29ycA" class="cyc_term">PumpingFluid</a>) may be instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEhJwpEbGdrcN5Y29ycA" class="cyc_term">FluidFlow_Translation</a>. Instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjYRJwpEbGdrcN5Y29ycA" class="cyc_term">CausingAnotherObjectsTranslationalMotion</a> include a train transporting passengers, a person pushing a coin into a vending machine, the release of a bowstring which propels an arrow, and a magnet attracting a nail. CausingAnotherObjectsTranslationalMotion

A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvjJE4ZwpEbGdrcN5Y29ycA" class="cyc_term">Event_Localized</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWESd5wpEbGdrcN5Y29ycA" class="cyc_term">IntrinsicStateChangeEvent</a> is an event characterized primarily by a change in some intrinsic property of at least one main actor involved in the event. Such intrinsic changes may include changes of a thing's color, temperature, device state, or size. Events where the main change is extrinsic (such as a change in location or ownership) are not instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWESd5wpEbGdrcN5Y29ycA" class="cyc_term">IntrinsicStateChangeEvent</a>. In events which have more than one actor, the event may be an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWESd5wpEbGdrcN5Y29ycA" class="cyc_term">IntrinsicStateChangeEvent</a> for one actor but not for another. For example, in a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjwqZwpEbGdrcN5Y29ycA" class="cyc_term">FasteningSafetyBelt</a> event, the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViLD5wpEbGdrcN5Y29ycA" class="cyc_term">SafetySeatBelt</a> (the device used) goes from unconnected to connected (to itself), which is an intrinsic change; however, the agent who does the fastening does not change intrinsically, but only in his configuration to the belt, an external object. Another example: in a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViw4JwpEbGdrcN5Y29ycA" class="cyc_term">HairCuttingEvent</a>, the hair that is cut undergoes an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWESd5wpEbGdrcN5Y29ycA" class="cyc_term">IntrinsicStateChangeEvent</a> due to its role in that kind of event, but the barber undergoes no intrinsic change due to the hair cutting. Note that some events, such as an ice cube melting into a small puddle of water, could be represented either as an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWESd5wpEbGdrcN5Y29ycA" class="cyc_term">IntrinsicStateChangeEvent</a> or as a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVibApwpEbGdrcN5Y29ycA" class="cyc_term">PhysicalTransformationEvent</a>, but not (within a single micro-theory) as both. event that inherently involves a change of state IntrinsicStateChangeEvent

inputsCommitted A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi3DZwpEbGdrcN5Y29ycA" class="cyc_term">inputs</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkH8JwpEbGdrcN5Y29ycA" class="cyc_term">commitsForFutureUses</a> that is used to state that an input (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi3DZwpEbGdrcN5Y29ycA" class="cyc_term">inputs</a>) to an event is incorporated into some output (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViYA5wpEbGdrcN5Y29ycA" class="cyc_term">outputs</a>) of that event, but remains recognizable rather than being destroyed. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWPtrJwpEbGdrcN5Y29ycA" class="cyc_term">inputsCommitted</a> EVENT OBJECT)</code> means that <code>OBJECT</code> exists before <code>EVENT</code> and continues to exist afterwards, and as a result of <code>EVENT</code>, <code>OBJECT</code> becomes incorporated into something created during <code>EVENT</code>. Once incorporated into the output of <code>EVENT</code>, <code>OBJECT</code> can't be independently incorporated in any other creation event. For example, bricks that are used to build a wall continue to exist as bricks once the wall has been built. While a part of the wall, a brick cannot be used as an independent input in another creation event. (See also <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWStbZwpEbGdrcN5Y29ycA" class="cyc_term">outputsCreated</a>.) Note that there is a grey area between <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWPtrJwpEbGdrcN5Y29ycA" class="cyc_term">inputsCommitted</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWWNUJwpEbGdrcN5Y29ycA" class="cyc_term">inputsDestroyed</a>; the less possible it is to take apart the relevant <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViYA5wpEbGdrcN5Y29ycA" class="cyc_term">outputs</a> of <code>EVENT</code> and get <code>OBJECT</code> back as an independent thing, the more likely it is that the relationship between <code>EVENT</code> and <code>OBJECT</code> should be <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWWNUJwpEbGdrcN5Y29ycA" class="cyc_term">inputsDestroyed</a>, rather than <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWPtrJwpEbGdrcN5Y29ycA" class="cyc_term">inputsCommitted</a>. input incorporated into the end result

An assertion of the form (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r8xywwgtGQdmDAZRxsM9bqw" class="cyc_term">fromAgent</a> TRANS AGENT) means that the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rDbKaOuVmQdeTKaYmT-4jgg" class="cyc_term">transferredThing</a> in the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOtpwpEbGdrcN5Y29ycA" class="cyc_term">GeneralizedTransfer</a> TRANS orginates with the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvsaaeJwpEbGdrcN5Y29ycA" class="cyc_term">Agent_Generic</a> AGENT. This is a very general relation and does not assume that AGENT has any rights over the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rDbKaOuVmQdeTKaYmT-4jgg" class="cyc_term">transferredThing</a>. See the more specialized predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVmEgpwpEbGdrcN5Y29ycA" class="cyc_term">fromPossessor</a> for cases where the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViknpwpEbGdrcN5Y29ycA" class="cyc_term">SocialBeing</a> has user rights over the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rDbKaOuVmQdeTKaYmT-4jgg" class="cyc_term">transferredThing</a>. From Agent fromAgent

translation A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOcJwpEbGdrcN5Y29ycA" class="cyc_term">Movement_TranslationEvent</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVsNyJwpEbGdrcN5Y29ycA" class="cyc_term">Translation_SingleTrajectory</a> is a translational movement that involves exactly one <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv_YPjpwpEbGdrcN5Y29ycA" class="cyc_term">trajectory_Complete</a>. One or more items might have the role of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a> in such an event. Note that although there is a single <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv_YPjpwpEbGdrcN5Y29ycA" class="cyc_term">trajectory_Complete</a>, it does not follow that there is a unique place in the role of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjiI5wpEbGdrcN5Y29ycA" class="cyc_term">fromLocation</a> or <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjXepwpEbGdrcN5Y29ycA" class="cyc_term">toLocation</a> because that depends on our descriptions of these locations. (E.g. the same single-trajectory movement can be described as from Texas to Pennsylvania, from Austin to Pittsburgh, or from northwest Austin to south Pittsburgh.) However, the single <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv_YPjpwpEbGdrcN5Y29ycA" class="cyc_term">trajectory_Complete</a> connects one from-location and one to-location. (Similarly, there may be a single existing <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViCe5wpEbGdrcN5Y29ycA" class="cyc_term">motionPathway_Complete</a> that the trajectory goes along, or a single <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvpsjd5wpEbGdrcN5Y29ycA" class="cyc_term">Traversal</a> of paths indicated by <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv3hJiZwpEbGdrcN5Y29ycA" class="cyc_term">traverses_Complete</a>.) Note that a translational motion performed by a whole <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjmoJwpEbGdrcN5Y29ycA" class="cyc_term">Group</a> is likely to be a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVsNyJwpEbGdrcN5Y29ycA" class="cyc_term">Translation_SingleTrajectory</a>; e.g. a flock of birds flying together or a snarl of rush-hour traffic on the Beltway. Non-examples include an opening break in a game of billiards and a group of water droplets coming together into one big drop. Contrast with <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV74r5wpEbGdrcN5Y29ycA" class="cyc_term">Translation_MultiTrajectory</a>. Translation-SingleTrajectory

transfer event with well-defined to-location A collection of events. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWMZaZwpEbGdrcN5Y29ycA" class="cyc_term">TransferIn</a> is a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOtpwpEbGdrcN5Y29ycA" class="cyc_term">GeneralizedTransfer</a> (q.v.) for which there is a well-defined thing that it is a transfer "to" (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwAyrYZwpEbGdrcN5Y29ycA" class="cyc_term">to_Generic</a>), but not necessarily a well-defined thing that it is a transfer "from" (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv9UIFZwpEbGdrcN5Y29ycA" class="cyc_term">from_Generic</a>). Subcollections of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWMZaZwpEbGdrcN5Y29ycA" class="cyc_term">TransferIn</a> include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjcHpwpEbGdrcN5Y29ycA" class="cyc_term">Collecting</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWRg15wpEbGdrcN5Y29ycA" class="cyc_term">GainingUserRights</a>, and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjWH5wpEbGdrcN5Y29ycA" class="cyc_term">AccessingAnIBT</a>. At the end of a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWMZaZwpEbGdrcN5Y29ycA" class="cyc_term">TransferIn</a>, the thing transferred (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rDbKaOuVmQdeTKaYmT-4jgg" class="cyc_term">transferredThing</a>) is in some sense "located" at the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwAyrYZwpEbGdrcN5Y29ycA" class="cyc_term">to_Generic</a>. Non- examples of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWMZaZwpEbGdrcN5Y29ycA" class="cyc_term">TransferIn</a> include instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWe33pwpEbGdrcN5Y29ycA" class="cyc_term">AbandoningSomething</a> (when there is no prospective owner) and of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvXDRVpwpEbGdrcN5Y29ycA" class="cyc_term">IBTGeneration</a> (when the information may go to various unspecified locations). TransferIn

<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwDQEV5wpEbGdrcN5Y29ycA" class="cyc_term">EconomicEvent</a> is the most general collection of events having an economic character, such as buying and selling, inflation and recession, and economic policy-making. EconomicEvent economic occurrence

moving object objectMoving The predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a> relates movement events to the object or objects moving in those events. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a> MOVE OBJECT)</code> means that <code>OBJECT</code> is in motion at some point during the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEAZwpEbGdrcN5Y29ycA" class="cyc_term">MovementEvent</a> <code>MOVE</code> and is either the primary object moving (see the predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvXxi65wpEbGdrcN5Y29ycA" class="cyc_term">primaryObjectMoving</a>) in <code>MOVE</code> or the primary object moving in some sub-event (see the predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViQmZwpEbGdrcN5Y29ycA" class="cyc_term">subEvents</a>) of <code>MOVE</code>.

An <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAKZwpEbGdrcN5Y29ycA" class="cyc_term">ActorSlot</a> that relates a "transfer" event of any sort (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOtpwpEbGdrcN5Y29ycA" class="cyc_term">GeneralizedTransfer</a>) to a spatial path (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwJXokJwpEbGdrcN5Y29ycA" class="cyc_term">Path_Spatial</a>) that is followed during at least part of the event. More formally, <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv2yvB5wpEbGdrcN5Y29ycA" class="cyc_term">genericPathway_Partial</a> TRANS PATH)</code> means that at least part of the route of <code>TRANS</code> is spatial, and at least part of this part follows a part of <code>PATH</code>. For example, if a certain trip <code>TRANS</code> takes a person from a home in Austin to one in Dallas via (mostly) I-35, part of the trip may occur along highways other than I-35 and part of it will occur along ordinary streets in Austin and Dallas. Thus only part of <code>TRANS</code> occurs along I-35. We may represent this in CycL by stating <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv2yvB5wpEbGdrcN5Y29ycA" class="cyc_term">genericPathway_Partial</a> TRANS Interstate35)</code>. As another example, consider an e-mail sent from one PC to another. Suppose this transfer of information <code>INFOTRANS</code> occurs along several distinct cables. If one of these cables is <code>CABLE001</code>, then we may correctly assert <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv2yvB5wpEbGdrcN5Y29ycA" class="cyc_term">genericPathway_Partial</a> INFOTRANS CABLE001)</code>. See also <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwDypxJwpEbGdrcN5Y29ycA" class="cyc_term">genericPathway_Complete</a> and its #$cyclistNotes for a comparison with this predicate. Note that in both examples above, it would be incorrect to replace <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv2yvB5wpEbGdrcN5Y29ycA" class="cyc_term">genericPathway_Partial</a> with <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwDypxJwpEbGdrcN5Y29ycA" class="cyc_term">genericPathway_Complete</a>, since the entire transfers did not occur along I-35 and <code>CABLE001</code>, respectively. See also the more specific predicates <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvt3H_5wpEbGdrcN5Y29ycA" class="cyc_term">infoPathway_Partial</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv_QFmJwpEbGdrcN5Y29ycA" class="cyc_term">motionPathway_Partial</a>. partial pathway used genericPathway-Partial

A <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViCxpwpEbGdrcN5Y29ycA" class="cyc_term">SubEventPredicate</a> that is a specialization of both <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rMfpoxnOxQdiInZcva6xBew" class="cyc_term">properSubEvents</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r9JeCFoUIQdiYiLW7AUcKGA" class="cyc_term">firstProperSubSituations</a> (qq.v.). (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjWoJwpEbGdrcN5Y29ycA" class="cyc_term">firstSubEvents</a> EVENT START) means that START is a beginning part of EVENT. That is, START is a proper subevent of EVENT that starts exactly when EVENT starts and ends before EVENT ends. Also, START should be something that it would seem intuitively correct (in the context in question) to describe as "the first part" of EVENT. Typically, START ends no later than halfway through (i.e. the temporal mid-point of) the occurring of EVENT. Note that more than one event might be considered a first part of a given event; for example, either the first inning or the first pitch of the first inning could be considered a first subevent of a baseball game. See also <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjXppwpEbGdrcN5Y29ycA" class="cyc_term">lastSubEvents</a>. firstSubEvents first subevent

The predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV0FMZwpEbGdrcN5Y29ycA" class="cyc_term">deviceUsed</a> relates an event to a device used in that event. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV0FMZwpEbGdrcN5Y29ycA" class="cyc_term">deviceUsed</a> EVENT OBJECT)</code> means that the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjHL5wpEbGdrcN5Y29ycA" class="cyc_term">PhysicalDevice</a> <code>OBJECT</code> plays an instrumental role in the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a> <code>EVENT</code> (see the more generalized predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV1Os5wpEbGdrcN5Y29ycA" class="cyc_term">instrument_Generic</a>), <code>OBJECT</code> is intentionally used in <code>EVENT</code>, and standardly (for example, in the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj-c5wpEbGdrcN5Y29ycA" class="cyc_term">HumanActivitiesMt</a>) <code>OBJECT</code>'s role in <code>EVENT</code> is consistent with the object's <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv-lujZwpEbGdrcN5Y29ycA" class="cyc_term">primaryFunction</a>. device used deviceUsed

Translocation A subcollection of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEAZwpEbGdrcN5Y29ycA" class="cyc_term">MovementEvent</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv4GokJwpEbGdrcN5Y29ycA" class="cyc_term">Translocation</a> is a movement across a distance; thus there is both a location that it is a movement "from" (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjiI5wpEbGdrcN5Y29ycA" class="cyc_term">fromLocation</a>) and a location that it is a movement "to" (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjXepwpEbGdrcN5Y29ycA" class="cyc_term">toLocation</a>). (These two locations might or might not be distinct, considering round-trips.) Note that instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv4GokJwpEbGdrcN5Y29ycA" class="cyc_term">Translocation</a> might or might not involve a salient moving object (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a>); for those that do see the specialization <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOcJwpEbGdrcN5Y29ycA" class="cyc_term">Movement_TranslationEvent</a>; for some that don't see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwQCA9ZwpEbGdrcN5Y29ycA" class="cyc_term">WavePropagation</a>. translocation

subprocess A <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViCxpwpEbGdrcN5Y29ycA" class="cyc_term">SubEventPredicate</a> and a specialization of both <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWn4OZwpEbGdrcN5Y29ycA" class="cyc_term">timeSlices</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViQmZwpEbGdrcN5Y29ycA" class="cyc_term">subEvents</a> (qq.v.). (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwCK6fZwpEbGdrcN5Y29ycA" class="cyc_term">subProcesses</a> EVENT SUBPROCESS) means that SUBPROCESS is a subevent of EVENT that consists of everything that "happens in" EVENT during the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAw5wpEbGdrcN5Y29ycA" class="cyc_term">TimeInterval</a> that SUBPROCESS occurs. subProcesses

Event Overlaps eventOverlaps This predicate relates overlapping events. (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvrlIZJwpEbGdrcN5Y29ycA" class="cyc_term">eventOverlaps</a> EVENT1 EVENT2) means that EVENT1 and EVENT2 share a common subevent. That is, there is a SUBEVENT such that both (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViQmZwpEbGdrcN5Y29ycA" class="cyc_term">subEvents</a> EVENT1 SUBEVENT) and (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViQmZwpEbGdrcN5Y29ycA" class="cyc_term">subEvents</a> EVENT2 SUBEVENT) hold.

A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a>. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvjJE4ZwpEbGdrcN5Y29ycA" class="cyc_term">Event_Localized</a> is the collection of all events that occur at a specific location in space. Notable specializations of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvjJE4ZwpEbGdrcN5Y29ycA" class="cyc_term">Event_Localized</a> include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjpjZwpEbGdrcN5Y29ycA" class="cyc_term">PhysicalEvent</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViNqpwpEbGdrcN5Y29ycA" class="cyc_term">AnimalActivity</a>. localized event Event-Localized

Info Transferred A <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwL4_QpwpEbGdrcN5Y29ycA" class="cyc_term">BinaryRolePredicate</a> that is used to specify some or all of the meaningful content of a particular transferral of information (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVifB5wpEbGdrcN5Y29ycA" class="cyc_term">InformationTransferEvent</a>). <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWUq7JwpEbGdrcN5Y29ycA" class="cyc_term">infoTransferred</a> TRANSFER INFO)</code> means that <code>INFO</code> is information (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvf9sZJwpEbGdrcN5Y29ycA" class="cyc_term">AspatialInformationStore</a>) that is transferred due to <code>TRANSFER</code>. <code>INFO</code> originates (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV5PA5wpEbGdrcN5Y29ycA" class="cyc_term">informationOrigin</a>) from some agent or <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvkNufpwpEbGdrcN5Y29ycA" class="cyc_term">InformationBearingThing</a> ("IBT") and, after <code>TRANSFER</code>, is had by another agent or is contained in another IBT (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVipxZwpEbGdrcN5Y29ycA" class="cyc_term">informationDestination</a>); <code>INFO</code> may persist in the origin as well. For example, when I read the front page of the newspaper, some information about current world events is transferred from the newspaper to me. infoTransferred

A specialization of both <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV2sVpwpEbGdrcN5Y29ycA" class="cyc_term">Movement_NonPeriodic</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOcJwpEbGdrcN5Y29ycA" class="cyc_term">Movement_TranslationEvent</a>. In each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv7_nWZwpEbGdrcN5Y29ycA" class="cyc_term">Translation_NonPeriodic</a>, the moving object (see the predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a>) is in translational motion and does not move back to the same position on a regular temporal basis (it can visit the same location multiple times, just not regularly). non-periodic translation Translation-NonPeriodic

topic The predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVzuRJwpEbGdrcN5Y29ycA" class="cyc_term">topicOfInfoTransfer</a> is used to indicate what a particular communication is about. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVzuRJwpEbGdrcN5Y29ycA" class="cyc_term">topicOfInfoTransfer</a> TRANS TOPIC)</code> means that <code>TOPIC</code> is a primary topic of the information communicated in the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVifB5wpEbGdrcN5Y29ycA" class="cyc_term">InformationTransferEvent</a> <code>TRANS</code>. For example, a result reported after an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1YgpwpEbGdrcN5Y29ycA" class="cyc_term">BloodTest</a> will contain information about the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1YAZwpEbGdrcN5Y29ycA" class="cyc_term">objectTested</a> (viz., the blood sample); the patient's blood is thus a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVzuRJwpEbGdrcN5Y29ycA" class="cyc_term">topicOfInfoTransfer</a> of that report. topicOfInfoTransfer

A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvjJE4ZwpEbGdrcN5Y29ycA" class="cyc_term">Event_Localized</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjpjZwpEbGdrcN5Y29ycA" class="cyc_term">PhysicalEvent</a> is a spatially localized event involving one or more physical objects or stuffs. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjpjZwpEbGdrcN5Y29ycA" class="cyc_term">PhysicalEvent</a>s typically involve interaction among <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj27ZwpEbGdrcN5Y29ycA" class="cyc_term">PartiallyTangible</a>s. But note that a physical event might consist in the creation, destruction, movement, or a change in some physical feature of a single salient physical object. (See <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvpKVWpwpEbGdrcN5Y29ycA" class="cyc_term">PhysicalCreationEvent</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv4jqZJwpEbGdrcN5Y29ycA" class="cyc_term">PhysicalDestructionEvent</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEAZwpEbGdrcN5Y29ycA" class="cyc_term">MovementEvent</a>, and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWESd5wpEbGdrcN5Y29ycA" class="cyc_term">IntrinsicStateChangeEvent</a>.) For a contrasting (though not necessarily disjoint) collection, see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvkjZ1pwpEbGdrcN5Y29ycA" class="cyc_term">StrictlyMentalEvent</a>. For events that have both physical and mental components, see the collection <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViNJ5wpEbGdrcN5Y29ycA" class="cyc_term">CompositePhysicalAndMentalEvent</a>. physical event PhysicalEvent

A very general <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAKZwpEbGdrcN5Y29ycA" class="cyc_term">ActorSlot</a> predicate that relates events to the things that "do" them. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1HmJwpEbGdrcN5Y29ycA" class="cyc_term">doneBy</a> EVENT DOER)</code> means that <code>DOER</code> is a "doer" in the event <code>EVENT</code>: some activity on the part of <code>DOER</code> causes or carries out <code>EVENT</code>. This predicate is agnostic as to whether <code>DOER</code> does <code>EVENT</code> intentionally or not. Note that <code>DOER</code> need not even be animate or an agent; e.g. the famous vocanic eruption that buried Pompeii was <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1HmJwpEbGdrcN5Y29ycA" class="cyc_term">doneBy</a> Mt. Vesuvius. Note also that an event might have more than one doer; consider a chess game. See the specializations <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVipYpwpEbGdrcN5Y29ycA" class="cyc_term">performedBy</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV_GH5wpEbGdrcN5Y29ycA" class="cyc_term">bodilyDoer</a> for cases in which the "doer" is, respectively, an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvsaaeJwpEbGdrcN5Y29ycA" class="cyc_term">Agent_Generic</a> acting deliberately and an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjE1pwpEbGdrcN5Y29ycA" class="cyc_term">Organism_Whole</a> behaving non-deliberately. doneBy doer

action The collection of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a>s (q.v.) that are carried out by some "doer" (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1HmJwpEbGdrcN5Y29ycA" class="cyc_term">doneBy</a>). Instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVioQZwpEbGdrcN5Y29ycA" class="cyc_term">Action</a> include any event in which one or more actors effect some change in the (tangible or intangible) state of the world, typically by an expenditure of effort or energy. Note that it is not required that any tangible object be moved, changed, produced, or destroyed for an action to occur; the effects of an action might be intangible (such as a change in a bank balance or the intimidation of a subordinate). Note also that the doer of an action, though typically an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAB5wpEbGdrcN5Y29ycA" class="cyc_term">Agent_PartiallyTangible</a> (q.v.), need not be (e.g. a falling rock that dents a car's roof). Depending upon the context, doers of actions might be animate or inanimate, conscious or nonconscious. For actions that are intentional, see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVieP5wpEbGdrcN5Y29ycA" class="cyc_term">PurposefulAction</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVipYpwpEbGdrcN5Y29ycA" class="cyc_term">performedBy</a>. Action

The predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV5SppwpEbGdrcN5Y29ycA" class="cyc_term">postActors</a> is used to indicate that a participant in an event continues to exist after that event is over. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV5SppwpEbGdrcN5Y29ycA" class="cyc_term">postActors</a> EVENT OBJECT)</code> means that <code>OBJECT</code> is a participant in <code>EVENT</code> (so that <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjFpZwpEbGdrcN5Y29ycA" class="cyc_term">actors</a> EVENT OBJECT)</code> also holds), and that <code>OBJECT</code> exists after <code>EVENT</code> ends. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV5SppwpEbGdrcN5Y29ycA" class="cyc_term">postActors</a> is a very general instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAKZwpEbGdrcN5Y29ycA" class="cyc_term">ActorSlot</a>; it subsumes <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWStbZwpEbGdrcN5Y29ycA" class="cyc_term">outputsCreated</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rDbKaOuVmQdeTKaYmT-4jgg" class="cyc_term">transferredThing</a>, and many others. postActors actor remaining afterwards

This predicate relates objects to the transportation events in which they facilitate movement. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjB2JwpEbGdrcN5Y29ycA" class="cyc_term">transporter</a> MOVE OBJ)</code> means that <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjElJwpEbGdrcN5Y29ycA" class="cyc_term">SolidTangibleThing</a> <code>OBJ</code> enables or facilitates the conveyance of the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViulJwpEbGdrcN5Y29ycA" class="cyc_term">transportees</a> in the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv-6HepwpEbGdrcN5Y29ycA" class="cyc_term">TransportationEvent</a> <code>MOVE</code>. <code>OBJ</code> is an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a> in <code>MOVE</code> that moves along with the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViulJwpEbGdrcN5Y29ycA" class="cyc_term">transportees</a>. <code>OBJ</code> will generally hold, support, contain, pull, or push the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViulJwpEbGdrcN5Y29ycA" class="cyc_term">transportees</a> throughout the <code>MOVE</code> <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a>. <code>OBJ</code> may or may not be the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjX_pwpEbGdrcN5Y29ycA" class="cyc_term">providerOfMotiveForce</a> in the event <code>MOVE</code>. If <code>OBJ</code> stays with each <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvXxi65wpEbGdrcN5Y29ycA" class="cyc_term">primaryObjectMoving</a> from the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjiI5wpEbGdrcN5Y29ycA" class="cyc_term">fromLocation</a> to the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjXepwpEbGdrcN5Y29ycA" class="cyc_term">toLocation</a>, moving along the same trajectory, then it is also a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvXxi65wpEbGdrcN5Y29ycA" class="cyc_term">primaryObjectMoving</a>. If <code>OBJ</code> facilitates the motion of the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvXxi65wpEbGdrcN5Y29ycA" class="cyc_term">primaryObjectMoving</a> but does not itself engage in translational motion it is merely the conveyor of the action, and the role <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwVgbe5wpEbGdrcN5Y29ycA" class="cyc_term">conveyor_Stationary</a> should be asserted. If it is unclear whether the conveyor is stationary or not, the role <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwPqxbJwpEbGdrcN5Y29ycA" class="cyc_term">conveyor_Generic</a> is used. Specializations of the role <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjB2JwpEbGdrcN5Y29ycA" class="cyc_term">transporter</a> should be used when possible: although automobiles are <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjB2JwpEbGdrcN5Y29ycA" class="cyc_term">transporter</a>s in many events, they should normally have the more specific role designation of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViog5wpEbGdrcN5Y29ycA" class="cyc_term">vehicle</a> because they are also instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwLzhaZwpEbGdrcN5Y29ycA" class="cyc_term">TransportationDevice_Vehicle</a>. When a car is being towed by a tow truck, the car is just a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjB2JwpEbGdrcN5Y29ycA" class="cyc_term">transporter</a> of any of its contents while the tow truck is the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViog5wpEbGdrcN5Y29ycA" class="cyc_term">vehicle</a> of that event. An additional role designation for some <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjB2JwpEbGdrcN5Y29ycA" class="cyc_term">transporter</a>s -- those which are <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjHL5wpEbGdrcN5Y29ycA" class="cyc_term">PhysicalDevice</a>s -- is <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV0FMZwpEbGdrcN5Y29ycA" class="cyc_term">deviceUsed</a>; e.g., the use of crutches in hobbling or ice skates in skating. See the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViBCZwpEbGdrcN5Y29ycA" class="cyc_term">comment</a> on <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv-6HepwpEbGdrcN5Y29ycA" class="cyc_term">TransportationEvent</a>. Note that an organism may be a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViulJwpEbGdrcN5Y29ycA" class="cyc_term">transportees</a> in a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjo0JwpEbGdrcN5Y29ycA" class="cyc_term">Bicycle</a> riding or <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1jVJwpEbGdrcN5Y29ycA" class="cyc_term">Skating</a> event as well as being the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjX_pwpEbGdrcN5Y29ycA" class="cyc_term">providerOfMotiveForce</a> in such cases. transporter transporter

event in which something is created or destroyed or both PhysicalCreationOrDestructionEvent A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWdRSZwpEbGdrcN5Y29ycA" class="cyc_term">CreationOrDestructionEvent</a>. During each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvfvhT5wpEbGdrcN5Y29ycA" class="cyc_term">PhysicalCreationOrDestructionEvent</a>, one or more physical objects (instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj27ZwpEbGdrcN5Y29ycA" class="cyc_term">PartiallyTangible</a>) come into or go out of existence. If the object created or destroyed in an event is not physical (e.g., if it is an agreement or a conceptual work), then the event should be an instance of the more general collection <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWdRSZwpEbGdrcN5Y29ycA" class="cyc_term">CreationOrDestructionEvent</a>.

postEvents A <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwL4_QpwpEbGdrcN5Y29ycA" class="cyc_term">BinaryRolePredicate</a> (q.v.) that relates one event to another that follows it. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi76ZwpEbGdrcN5Y29ycA" class="cyc_term">postEvents</a> BEFORE AFTER)</code> implies two things: (1) <code>BEFORE</code> occurs strictly before <code>AFTER</code>: <code>AFTER</code> starts after <code>BEFORE</code> has ended (see the generalization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi76ZwpEbGdrcN5Y29ycA" class="cyc_term">postEvents</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjQyZwpEbGdrcN5Y29ycA" class="cyc_term">startsAfterEndingOf</a>). (2) <code>BEFORE</code> and <code>AFTER</code> are significantly relevant to each other. This required "relevance" of the two arguments to each other is difficult to formalize but often intuitively clearcut. Sometimes <code>AFTER</code> is caused by <code>BEFORE</code>. For example, we might say (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi76ZwpEbGdrcN5Y29ycA" class="cyc_term">postEvents</a> TakingAShower001 ExitingShower001), but would not say (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi76ZwpEbGdrcN5Y29ycA" class="cyc_term">postEvents</a> BolshevikRelvolution DeathOfJohnLennon) since these two events are not at all relevant to each other. Post Events

The predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjXepwpEbGdrcN5Y29ycA" class="cyc_term">toLocation</a> is used to indicate the ending point of a particular movement. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjXepwpEbGdrcN5Y29ycA" class="cyc_term">toLocation</a> MOVE LOC)</code> means that <code>LOC</code> is where the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a> in <code>MOVE</code> (a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOcJwpEbGdrcN5Y29ycA" class="cyc_term">Movement_TranslationEvent</a>) is found when the event <code>MOVE</code> ends; the final location of the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a> in that event is <code>LOC</code>. The <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a> may or may not be <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwPusM5wpEbGdrcN5Y29ycA" class="cyc_term">Stationary</a> at <code>LOC</code>. If <code>MOVE</code> is a single-pathway translation (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVsNyJwpEbGdrcN5Y29ycA" class="cyc_term">Translation_SingleTrajectory</a>), then every <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a> in it is found at <code>LOC</code> when <code>MOVE</code> ends. If <code>MOVE</code> has multiple movers and multiple pathways (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV74r5wpEbGdrcN5Y29ycA" class="cyc_term">Translation_MultiTrajectory</a>), then at least some of the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a>(s) can be found at <code>LOC</code> at the end of <code>MOVE</code>. If <code>MOVE</code> is a fluid flow (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEhJwpEbGdrcN5Y29ycA" class="cyc_term">FluidFlow_Translation</a>), then at least some portion of the fluid <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a> can be found at location <code>LOC</code> at the end of <code>MOVE</code>. See also <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViCe5wpEbGdrcN5Y29ycA" class="cyc_term">motionPathway_Complete</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwPKiKZwpEbGdrcN5Y29ycA" class="cyc_term">pathConnects</a>. destination toLocation

Causes Sit Prop (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwQ4li5wpEbGdrcN5Y29ycA" class="cyc_term">causes_SitProp</a> SIT PROP) means that the situation SIT causes the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwRZBCJwpEbGdrcN5Y29ycA" class="cyc_term">CycLSentence_Assertible</a> PROP to become true. causes-SitProp

A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOcJwpEbGdrcN5Y29ycA" class="cyc_term">Movement_TranslationEvent</a>. In any instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV74r5wpEbGdrcN5Y29ycA" class="cyc_term">Translation_MultiTrajectory</a>, motion may occur simultaneously along two or more instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjRepwpEbGdrcN5Y29ycA" class="cyc_term">Trajectory</a> (which are not related by sub-trajectory relationships.) Therefore, there must be at least two <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a>s in such an event. There may be more than one <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjiI5wpEbGdrcN5Y29ycA" class="cyc_term">fromLocation</a> and/or more than one <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjXepwpEbGdrcN5Y29ycA" class="cyc_term">toLocation</a>. Instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV74r5wpEbGdrcN5Y29ycA" class="cyc_term">Translation_MultiTrajectory</a> include scattering, distributing, and collecting things. For example, all of the following exhibit multi-trajectory translation movements: a rainshower or snowfall; an exploding firework; water being ejected from a sprinkling system; the surrounding objects being sucked up by a tornado; participants running a 100K footrace; pool balls during the opening break. Cf. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVsNyJwpEbGdrcN5Y29ycA" class="cyc_term">Translation_SingleTrajectory</a>. multi-path translation Translation-MultiTrajectory

A collection of translational motion events; hence a subcollection of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOcJwpEbGdrcN5Y29ycA" class="cyc_term">Movement_TranslationEvent</a>. In each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWH3qpwpEbGdrcN5Y29ycA" class="cyc_term">Translation_Complete</a>, the entire moving object (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a>) moves from the place of origin (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjiI5wpEbGdrcN5Y29ycA" class="cyc_term">fromLocation</a>) to the destination (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjXepwpEbGdrcN5Y29ycA" class="cyc_term">toLocation</a>). That is, the object completely leaves the origin and relocates to the destination. The moving object may be either a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r_lvetnS5EdaAAACgyZzFrg" class="cyc_term">NonFluidlikeTangibleThing</a> (e.g. a baseball) or a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjR45wpEbGdrcN5Y29ycA" class="cyc_term">FluidTangibleThing</a> all of which moves from one place to another (e.g. the gasoline used to fill a gas tank). Another example: a single molecule of water flowing from point A to point B in a river. Non-examples: a river flowing from A to B (the river itself is not relocated); a rubber band stretching. A borderline case: a spider spins a web, leaving part of itself, in effect, extended out behind it; in most contexts that would still be considered a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWH3qpwpEbGdrcN5Y29ycA" class="cyc_term">Translation_Complete</a>. Note that <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWH3qpwpEbGdrcN5Y29ycA" class="cyc_term">Translation_Complete</a> is noncommittal as to whether net movement has occurred, so round-trip events qualify as complete translations (cf. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV-BF5wpEbGdrcN5Y29ycA" class="cyc_term">Translation_LocationChange</a>). complete translation Translation-Complete

from-Generic <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv9UIFZwpEbGdrcN5Y29ycA" class="cyc_term">from_Generic</a> GEN-TRANS THING)</code> means that the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOtpwpEbGdrcN5Y29ycA" class="cyc_term">GeneralizedTransfer</a> <code>GEN-TRANS</code> has an origin or starting point <code>THING</code>. Because <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOtpwpEbGdrcN5Y29ycA" class="cyc_term">GeneralizedTransfer</a> covers many kinds of transfer, both physical and abstract, this starting point can be of many types. In a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv4GokJwpEbGdrcN5Y29ycA" class="cyc_term">Translocation</a> it is a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj27ZwpEbGdrcN5Y29ycA" class="cyc_term">PartiallyTangible</a> location (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjiI5wpEbGdrcN5Y29ycA" class="cyc_term">fromLocation</a>), while in <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViM85wpEbGdrcN5Y29ycA" class="cyc_term">TransferringPossession</a> it is an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvsaaeJwpEbGdrcN5Y29ycA" class="cyc_term">Agent_Generic</a> (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVmEgpwpEbGdrcN5Y29ycA" class="cyc_term">fromPossessor</a>). <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv9UIFZwpEbGdrcN5Y29ycA" class="cyc_term">from_Generic</a> encompasses all kinds of starting points; as a rule, it is better to use more the specific predicates when possible. From-Generic

trajectoryPassesThrough thing passed through An <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAKZwpEbGdrcN5Y29ycA" class="cyc_term">ActorSlot</a> and a specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV5E85wpEbGdrcN5Y29ycA" class="cyc_term">nonDeliberateActors</a>. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv9b66pwpEbGdrcN5Y29ycA" class="cyc_term">trajectoryPassesThrough</a> MOVE LOC)</code> means that the trajectory (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv_YPjpwpEbGdrcN5Y29ycA" class="cyc_term">trajectory_Complete</a>) of the object moving (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a>) <code>OBJ</code> in the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVsNyJwpEbGdrcN5Y29ycA" class="cyc_term">Translation_SingleTrajectory</a> <code>MOVE</code> passes through the location (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4ro3lluGJHQdiVxrZReHS-jQ" class="cyc_term">EnduringThing_Localized</a>) <code>LOC</code>. Here "passes through <code>LOC</code>" implies that, in the course of moving from its <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjiI5wpEbGdrcN5Y29ycA" class="cyc_term">fromLocation</a> to its <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjXepwpEbGdrcN5Y29ycA" class="cyc_term">toLocation</a>, <code>OBJ</code> first arrives in and then leaves <code>LOC</code>. Note that <code>LOC</code> is not constrained to be <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvm22zpwpEbGdrcN5Y29ycA" class="cyc_term">spatiallyDisjoint</a> with this from-location or to-location; <code>LOC</code> might even subsume (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv9FMG5wpEbGdrcN5Y29ycA" class="cyc_term">spatiallySubsumes</a>) either of them. Thus, if (say) <code>LOC</code> subsumes the from-location, <code>OBJ</code> must first leave <code>LOC</code>, then arrive back in <code>LOC</code>, and then leave <code>LOC</code> again in order to pass through it. Also note that <code>LOC</code> must be <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwPusM5wpEbGdrcN5Y29ycA" class="cyc_term">Stationary</a> during <code>MOVE</code>, relative to the associated <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjUoJwpEbGdrcN5Y29ycA" class="cyc_term">FrameOfReference</a>.

Recipient Of Info Intended recipientOfInfo-Intended A specialization of both <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVqYY5wpEbGdrcN5Y29ycA" class="cyc_term">recipientOfInfo</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVwuhZwpEbGdrcN5Y29ycA" class="cyc_term">communicationTarget</a> that is used to indicate who among those who receive information in a communication event were also intended to receive the information. (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv7XiW5wpEbGdrcN5Y29ycA" class="cyc_term">recipientOfInfo_Intended</a> COMM RECIPIENT) holds whenever (i) RECIPIENT successfully receives the information communicated in the communication event COMM (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVqYY5wpEbGdrcN5Y29ycA" class="cyc_term">recipientOfInfo</a>) and (ii) RECIPIENT is one of the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvsaaeJwpEbGdrcN5Y29ycA" class="cyc_term">Agent_Generic</a>s that the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViPLZwpEbGdrcN5Y29ycA" class="cyc_term">senderOfInfo</a> in the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVieg5wpEbGdrcN5Y29ycA" class="cyc_term">CommunicationAct_Single</a> COMM intended to receive the information (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVwuhZwpEbGdrcN5Y29ycA" class="cyc_term">communicationTarget</a>). For example, suppose I am speaking at a closed meeting to one or more persons on classified information and, unbeknownst to me, a spy outside the room is listening in and hears everything I am saying. If each of the persons in the meeting hears everything I am saying, then each bears the relation <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv7XiW5wpEbGdrcN5Y29ycA" class="cyc_term">recipientOfInfo_Intended</a> to each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVieg5wpEbGdrcN5Y29ycA" class="cyc_term">CommunicationAct_Single</a> COMM during the meeting of which I am the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViPLZwpEbGdrcN5Y29ycA" class="cyc_term">senderOfInfo</a>. The spy, however, bears only the relation <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVqYY5wpEbGdrcN5Y29ycA" class="cyc_term">recipientOfInfo</a> to each of these instances. Suppose, however, that one person at the meeting is hard of hearing and does not hear what I am saying. Each event COMM is still a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVieg5wpEbGdrcN5Y29ycA" class="cyc_term">CommunicationAct_Single</a> since it had at least one <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViQmZwpEbGdrcN5Y29ycA" class="cyc_term">subEvents</a> that is an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjWH5wpEbGdrcN5Y29ycA" class="cyc_term">AccessingAnIBT</a> (at least the spy heard what was said) but the person who is hard of hearing is a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVwuhZwpEbGdrcN5Y29ycA" class="cyc_term">communicationTarget</a> of COMM but not a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv7XiW5wpEbGdrcN5Y29ycA" class="cyc_term">recipientOfInfo_Intended</a> since he or she did not receive the information, i.e. was not a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVqYY5wpEbGdrcN5Y29ycA" class="cyc_term">recipientOfInfo</a>. See also <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjggpwpEbGdrcN5Y29ycA" class="cyc_term">intendedAudience</a>.

MovementEvent A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOtpwpEbGdrcN5Y29ycA" class="cyc_term">GeneralizedTransfer</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvjKor5wpEbGdrcN5Y29ycA" class="cyc_term">MovementOrShapeChangeEvent</a> (qq.v.). This is the most general collection of physical movements. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEAZwpEbGdrcN5Y29ycA" class="cyc_term">MovementEvent</a> is an event in which at least one object (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a>) either translates some distance or moves from one rotational orientation to another, relative to a frame of reference that is not part of the translating/rotating object. The movement in question might be periodic or not, continuous or not. Notable specializations of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEAZwpEbGdrcN5Y29ycA" class="cyc_term">MovementEvent</a> include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv4GokJwpEbGdrcN5Y29ycA" class="cyc_term">Translocation</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjLCpwpEbGdrcN5Y29ycA" class="cyc_term">Movement_Rotation</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWWHKZwpEbGdrcN5Y29ycA" class="cyc_term">Movement_Periodic</a>, and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViQzZwpEbGdrcN5Y29ycA" class="cyc_term">MovementProcess</a>. movement

TransferOut A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOtpwpEbGdrcN5Y29ycA" class="cyc_term">GeneralizedTransfer</a>. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvcFjVpwpEbGdrcN5Y29ycA" class="cyc_term">TransferOut</a> includes all instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOtpwpEbGdrcN5Y29ycA" class="cyc_term">GeneralizedTransfer</a> in which some object plays the role of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv9UIFZwpEbGdrcN5Y29ycA" class="cyc_term">from_Generic</a>, but in which there may or may not be any object playing the role of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwAyrYZwpEbGdrcN5Y29ycA" class="cyc_term">to_Generic</a>. At the start of a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvcFjVpwpEbGdrcN5Y29ycA" class="cyc_term">TransferOut</a>, the object playing the role of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rDbKaOuVmQdeTKaYmT-4jgg" class="cyc_term">transferredThing</a> is 'located' at the object playing the role of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv9UIFZwpEbGdrcN5Y29ycA" class="cyc_term">from_Generic</a>. The collection <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvcFjVpwpEbGdrcN5Y29ycA" class="cyc_term">TransferOut</a> includes, among other things, all instances of the collections <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvtAG-JwpEbGdrcN5Y29ycA" class="cyc_term">Emission</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWQcoZwpEbGdrcN5Y29ycA" class="cyc_term">LosingUserRights</a>, and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj9a5wpEbGdrcN5Y29ycA" class="cyc_term">DistributionEvent</a>. Negative examples of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvcFjVpwpEbGdrcN5Y29ycA" class="cyc_term">TransferOut</a> include some instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjuo5wpEbGdrcN5Y29ycA" class="cyc_term">AppropriatingSomething</a> (when there is no previous owner) and some instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjcMpwpEbGdrcN5Y29ycA" class="cyc_term">Hearing</a> (when the sounds may come from various unspecified locations). transfer event with well-defined from-location

AtLeastPartiallyMentalEvent partially mental event A collection of events. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViGFZwpEbGdrcN5Y29ycA" class="cyc_term">AtLeastPartiallyMentalEvent</a> is an event involving the mental functions of a participant or group of participants (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjFpZwpEbGdrcN5Y29ycA" class="cyc_term">actors</a>) in that event. The collection includes such things as dreaming, perceiving, sensing, theorizing about something, having a realization, making a decision, building something, designing something, and consciously carrying out a task. Note that the above list includes both purposeful events and non-purposeful events that involve mental functions. Note also that any event that has a mental component is also an instance of this collection, so that events like preparing lunch would be classified as instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViGFZwpEbGdrcN5Y29ycA" class="cyc_term">AtLeastPartiallyMentalEvent</a>. In entering knowledge, it is almost always possible and preferable to use one of the specializations of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViGFZwpEbGdrcN5Y29ycA" class="cyc_term">AtLeastPartiallyMentalEvent</a>. If an event seems mostly mental in nature, modulo neurons firing and related brain activity, use <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvkjZ1pwpEbGdrcN5Y29ycA" class="cyc_term">StrictlyMentalEvent</a> or one of its specializations. If it essentially involves both mental and physical activity, see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViNJ5wpEbGdrcN5Y29ycA" class="cyc_term">CompositePhysicalAndMentalEvent</a> or <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvrOVYpwpEbGdrcN5Y29ycA" class="cyc_term">PurposefulPhysicalAction</a>. For mental events that are intentionally and purposefully performed, see the specialization <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwU3lVJwpEbGdrcN5Y29ycA" class="cyc_term">PurposefulMentalActivity</a>.

ActionOnObject action on an object A specialization of both <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVioQZwpEbGdrcN5Y29ycA" class="cyc_term">Action</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjpjZwpEbGdrcN5Y29ycA" class="cyc_term">PhysicalEvent</a>; the collection of physical events in which some doer acts on an object. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwOf2ypwpEbGdrcN5Y29ycA" class="cyc_term">ActionOnObject</a> is an action in which both the roles of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1HmJwpEbGdrcN5Y29ycA" class="cyc_term">doneBy</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi65pwpEbGdrcN5Y29ycA" class="cyc_term">objectActedOn</a> (qq.v.) are filled. Examples include someone typing on a keyboard and a tornado destroying a building. Non-examples include a person dancing and wind blowing.

primaryObjectMoving primary moving object An <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAKZwpEbGdrcN5Y29ycA" class="cyc_term">ActorSlot</a> and a specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a> (q.v.) that is used to specify a focal object that is moving in a particular <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEAZwpEbGdrcN5Y29ycA" class="cyc_term">MovementEvent</a>. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvXxi65wpEbGdrcN5Y29ycA" class="cyc_term">primaryObjectMoving</a> MOVE OBJECT)</code> means that <code>OBJECT</code> is in motion at some point during the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEAZwpEbGdrcN5Y29ycA" class="cyc_term">MovementEvent</a> <code>MOVE</code> and this movement is focal in <code>MOVE</code>. <code>OBJECT</code> moves from the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjiI5wpEbGdrcN5Y29ycA" class="cyc_term">fromLocation</a> to the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjXepwpEbGdrcN5Y29ycA" class="cyc_term">toLocation</a>. <code>OBJECT</code>'s motion in <code>MOVE</code> may be translational, rotational, or some combination of these. <code>OBJECT</code> may be a solid (such as an animal, an automobile, or a tennis ball) or a fluid (such as lava flowing or a warm air mass rising) -- but must be <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj27ZwpEbGdrcN5Y29ycA" class="cyc_term">PartiallyTangible</a>. If a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjmoJwpEbGdrcN5Y29ycA" class="cyc_term">Group</a> of objects is moving along the same trajectory, that <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjmoJwpEbGdrcN5Y29ycA" class="cyc_term">Group</a>, each <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjEZpwpEbGdrcN5Y29ycA" class="cyc_term">subGroups</a>, and each member of that <code>GROUP</code> is a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvXxi65wpEbGdrcN5Y29ycA" class="cyc_term">primaryObjectMoving</a> in the movement. An individual part of a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvXxi65wpEbGdrcN5Y29ycA" class="cyc_term">primaryObjectMoving</a> may be but is not necessarily an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a> in <code>MOVE</code>. An object contained by a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvXxi65wpEbGdrcN5Y29ycA" class="cyc_term">primaryObjectMoving</a> is generally, but not always, also a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvXxi65wpEbGdrcN5Y29ycA" class="cyc_term">primaryObjectMoving</a> in the same event. Other objects moving in the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEAZwpEbGdrcN5Y29ycA" class="cyc_term">MovementEvent</a> are referred to by the more general predicate, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a>. A <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjB2JwpEbGdrcN5Y29ycA" class="cyc_term">transporter</a> which follows a separate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjRepwpEbGdrcN5Y29ycA" class="cyc_term">Trajectory</a> (e.g. a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViMXJwpEbGdrcN5Y29ycA" class="cyc_term">Ladle</a>) or a conveyor which engages in a different form of motion (e.g. a rotating <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwQrmkJwpEbGdrcN5Y29ycA" class="cyc_term">ConveyorBelt</a> that translates a load) is not a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvXxi65wpEbGdrcN5Y29ycA" class="cyc_term">primaryObjectMoving</a> in the conveying event. Any <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a> in a particular event is a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvXxi65wpEbGdrcN5Y29ycA" class="cyc_term">primaryObjectMoving</a> in one or more <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViQmZwpEbGdrcN5Y29ycA" class="cyc_term">subEvents</a>.

lastSubEvents completion A <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViCxpwpEbGdrcN5Y29ycA" class="cyc_term">SubEventPredicate</a> that is a specialization of both <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rMfpoxnOxQdiInZcva6xBew" class="cyc_term">properSubEvents</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rQiMQLoUHQdiDr8E7cKVpJA" class="cyc_term">lastProperSubSituations</a> (qq.v.). (#$lastProperSubEvents EVENT END) means that END is a final part of EVENT. That is, END is a proper subevent of EVENT that starts after EVENT starts and ends exactly when EVENT ends. Also, END should be something that it would seem intuitively correct (in the context in question) to describe as "the last part" of EVENT. Typically, END doesn't start until at least halfway through (i.e. the temporal mid-point of) the occurring of EVENT. Note that more than one event might be considered a last part of a given event; for example, either the ninth inning or the last play of the ninth inning could be considered the last subevent of a baseball game. See also #$firstProperSubEvents.

causes-EventEvent A <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rEB191PkhQdec67fsB9ul7g" class="cyc_term">CausationPredicate</a> and specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwKJNS5wpEbGdrcN5Y29ycA" class="cyc_term">causes_SitSit</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv4MmhpwpEbGdrcN5Y29ycA" class="cyc_term">eventOutcomes</a> (qq.v.) that holds between two <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a>s. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv6fA45wpEbGdrcN5Y29ycA" class="cyc_term">causes_EventEvent</a> CAUSE EFFECT)</code> means that the event <code>CAUSE</code> was sufficient to cause the event <code>EFFECT</code>. See the shared #$NoteAboutCausationPredicates for a map of related causation predicates. consequence

<code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV-OCpwpEbGdrcN5Y29ycA" class="cyc_term">traverses_Partial</a> MOVE TRAV)</code> means that the moving object <code>OBJ</code> in the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVsNyJwpEbGdrcN5Y29ycA" class="cyc_term">Translation_SingleTrajectory</a> <code>MOVE</code> (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a>) is partially confined to the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvpsjd5wpEbGdrcN5Y29ycA" class="cyc_term">Traversal</a> <code>TRAV</code> during <code>MOVE</code>. To say that <code>OBJ</code> is partially confined to <code>TRAV</code> during <code>MOVE</code>, we mean that (1) there is a subevent <code>SUBEVENT</code> of <code>MOVE</code> such that <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvrmSz5wpEbGdrcN5Y29ycA" class="cyc_term">subTranslations_SingleTrajectory</a> MOVE SUBEVENT)</code> holds, and (2) there is a sub-Traversal <code>SUBTRAV</code> of <code>TRAV</code> (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvqrqy5wpEbGdrcN5Y29ycA" class="cyc_term">subTraversals</a>) such that <code>SUBEVENT</code> is confined to <code>SUBTRAV</code>, i.e., <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv3hJiZwpEbGdrcN5Y29ycA" class="cyc_term">traverses_Complete</a> SUBEVENT SUBTRAV)</code> holds. traverses-Partial partially traversed path

subEvents subevent The most general instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViCxpwpEbGdrcN5Y29ycA" class="cyc_term">SubEventPredicate</a>, this predicate relates a given event to the events that are its parts. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViQmZwpEbGdrcN5Y29ycA" class="cyc_term">subEvents</a> WHOLE PART)</code> means that <code>PART</code> is a part, or subevent, of <code>WHOLE</code>. Events can be decomposed into subevents events temporally, spatially, and in other ways; see the specializations of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViQmZwpEbGdrcN5Y29ycA" class="cyc_term">subEvents</a> for more on this. For decomposing an event in a purely temporal way, see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwCK6fZwpEbGdrcN5Y29ycA" class="cyc_term">subProcesses</a>.

A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjpjZwpEbGdrcN5Y29ycA" class="cyc_term">PhysicalEvent</a> whose instances include translational or rotational movements of whole objects (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEAZwpEbGdrcN5Y29ycA" class="cyc_term">MovementEvent</a>), objects changing shape (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvp78r5wpEbGdrcN5Y29ycA" class="cyc_term">ShapeChangeEvent</a>), as well as events in which salient parts of an object move or change shape in relation to the reference frame of the whole object. For example, although a ticking grandfather clock is not normally undergoing either a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEAZwpEbGdrcN5Y29ycA" class="cyc_term">MovementEvent</a> or a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvp78r5wpEbGdrcN5Y29ycA" class="cyc_term">ShapeChangeEvent</a>, it can still be said to be moving -- and thus undergoing a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvjKor5wpEbGdrcN5Y29ycA" class="cyc_term">MovementOrShapeChangeEvent</a> -- in virtue of the fact that a salient part of the clock, the pendulum, is swinging. (Of course, the pendulum itself is periodically undergoing <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjLCpwpEbGdrcN5Y29ycA" class="cyc_term">Movement_Rotation</a>, and the tip of the pendulum is undergoing a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOcJwpEbGdrcN5Y29ycA" class="cyc_term">Movement_TranslationEvent</a>.) As a negative example, a catatonic person should not be thought of as undergoing any <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvjKor5wpEbGdrcN5Y29ycA" class="cyc_term">MovementOrShapeChangeEvent</a>. Although blood moves through such a person's veins, her lungs expand and contract, and so on, these things would not normally be considered salient enough to entail that the person herself was undergoing a movement or shape change event. movement or shape change MovementOrShapeChangeEvent

This predicate relates an agent to an event in which that agent gains some right to use an object. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVipeZwpEbGdrcN5Y29ycA" class="cyc_term">toPossessor</a> GAIN AGENT)</code> means that immediately after the instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWRg15wpEbGdrcN5Y29ycA" class="cyc_term">GainingUserRights</a> <code>GAIN</code>, the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAB5wpEbGdrcN5Y29ycA" class="cyc_term">Agent_PartiallyTangible</a> <code>AGENT</code> enjoys being in some <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rIh5wwHSwEdaAAACgyZzFrg" class="cyc_term">SituationTypeByUserRights</a> over an object whose possession is transferred in <code>GAIN</code> (the object is related to <code>GAIN</code> via the predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj0z5wpEbGdrcN5Y29ycA" class="cyc_term">objectOfPossessionTransfer</a>), where the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rIh5wwHSwEdaAAACgyZzFrg" class="cyc_term">SituationTypeByUserRights</a> in question is one which <code>AGENT</code> did not have (at least with respect to the object transferred) at the start of <code>GAIN</code>. recipient toPossessor

origin An <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAKZwpEbGdrcN5Y29ycA" class="cyc_term">ActorSlot</a> that is a specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWDKWZwpEbGdrcN5Y29ycA" class="cyc_term">preActors</a> (q.v.). This predicate is used to indicate the starting point of a particular movement from one place to another. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjiI5wpEbGdrcN5Y29ycA" class="cyc_term">fromLocation</a> MOVE LOC)</code> means that <code>LOC</code> is where some salient moving-object (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a>) in the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv4GokJwpEbGdrcN5Y29ycA" class="cyc_term">Translocation</a> <code>MOVE</code> is found at the beginning of <code>MOVE</code> and is where it begins this motion. This moving-object might or might not be <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwPusM5wpEbGdrcN5Y29ycA" class="cyc_term">Stationary</a> at <code>LOC</code> at the beginning of <code>MOVE</code>. If <code>MOVE</code> is a single-pathway translation (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVsNyJwpEbGdrcN5Y29ycA" class="cyc_term">Translation_SingleTrajectory</a>), then each of its salient moving-objects is found at <code>LOC</code> when <code>MOVE</code> starts. If <code>MOVE</code> has multiple movers and multiple pathways (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV74r5wpEbGdrcN5Y29ycA" class="cyc_term">Translation_MultiTrajectory</a>), then at least some of the moving-objects can be found at <code>LOC</code> when <code>MOVE</code> starts. If <code>MOVE</code> is a flow (such as a river flowing, a wind blowing, a tornado, a typhoon, some clouds moving, or air filling your lungs when you take a breath; see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEhJwpEbGdrcN5Y29ycA" class="cyc_term">FluidFlow_Translation</a>), then at least some portion of the fluid moving-object can be found at <code>LOC</code> when <code>MOVE</code> starts. See also <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViCe5wpEbGdrcN5Y29ycA" class="cyc_term">motionPathway_Complete</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwPKiKZwpEbGdrcN5Y29ycA" class="cyc_term">pathConnects</a>. fromLocation

A specialization of both <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViYA5wpEbGdrcN5Y29ycA" class="cyc_term">outputs</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWDKWZwpEbGdrcN5Y29ycA" class="cyc_term">preActors</a> that relates physical destruction events to surviving parts of the things destroyed in those events. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWTgkpwpEbGdrcN5Y29ycA" class="cyc_term">outputsRemaining</a> EVENT OBJECT)</code> means that <code>OBJECT</code> persists after <code>EVENT</code>, and that it existed before <code>EVENT</code> as an identifiable part of one of the things destroyed during <code>EVENT</code> (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWWNUJwpEbGdrcN5Y29ycA" class="cyc_term">inputsDestroyed</a>). Examples: (1) when a sheet of plywood is sawn through, the original board is destroyed and the remaining-outputs are the two smaller plywood pieces; (2) when a mixture undergoes a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rP3AFIJ1FQdidOJS_SVP6IQ" class="cyc_term">FluidFiltrationProcess</a>, the mixture itself is destroyed, while both the material that was in suspension (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwPuam5wpEbGdrcN5Y29ycA" class="cyc_term">suspendedPart</a>) and the fluid it was suspended in (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwPuX4JwpEbGdrcN5Y29ycA" class="cyc_term">suspendingFluid</a>) are remaining-outputs. output remaining afterwards outputsRemaining

running DeviceRunning A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjpjZwpEbGdrcN5Y29ycA" class="cyc_term">PhysicalEvent</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViQRZwpEbGdrcN5Y29ycA" class="cyc_term">DeviceRunning</a> is an event in which some device is running. This collection includes events which are complete cycles of a device's normal function (see the specialization <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjHgJwpEbGdrcN5Y29ycA" class="cyc_term">SingleCompleteRunOfADevice</a>), as well as random time slices (see the predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWn4OZwpEbGdrcN5Y29ycA" class="cyc_term">timeSlices</a>) of such events. Examples of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViQRZwpEbGdrcN5Y29ycA" class="cyc_term">DeviceRunning</a> include instances of the collections <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViD85wpEbGdrcN5Y29ycA" class="cyc_term">AirplaneTakeOff</a>, #$SkateBoarding, and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwQCa2pwpEbGdrcN5Y29ycA" class="cyc_term">OffRoadMotorcycleRiding</a>. Note that an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViQRZwpEbGdrcN5Y29ycA" class="cyc_term">DeviceRunning</a> does not need to be a continuous event. Examples of discontinuous instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViQRZwpEbGdrcN5Y29ycA" class="cyc_term">DeviceRunning</a> include the following: the event of all the ignition phases of the firing of a particular automobile's engine during November of 1996; the event in which a particular TV was on and showing a commercial in the year 2001.

event location An <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAKZwpEbGdrcN5Y29ycA" class="cyc_term">ActorSlot</a> and a specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjXDJwpEbGdrcN5Y29ycA" class="cyc_term">inRegion</a> that relates a particular event to the instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4ro3lluGJHQdiVxrZReHS-jQ" class="cyc_term">EnduringThing_Localized</a> at which it occurs. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjVnpwpEbGdrcN5Y29ycA" class="cyc_term">eventOccursAt</a> EVENT LOC)</code> means that the spatial extent of <code>EVENT</code> is within <code>LOC</code>. For example, (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjVnpwpEbGdrcN5Y29ycA" class="cyc_term">eventOccursAt</a> LomaPrietaEarthquake SanFranciscoBayArea). See also the more general predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvxkrIZwpEbGdrcN5Y29ycA" class="cyc_term">eventPartiallyOccursAt</a>, which relates an event to any instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwS68M5wpEbGdrcN5Y29ycA" class="cyc_term">SpatialThing_Localized</a> in which some sub-event of it occurs. eventOccursAt

infoPathway-Partial An <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAKZwpEbGdrcN5Y29ycA" class="cyc_term">ActorSlot</a> and specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv2yvB5wpEbGdrcN5Y29ycA" class="cyc_term">genericPathway_Partial</a> that relates an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVifB5wpEbGdrcN5Y29ycA" class="cyc_term">InformationTransferEvent</a> to a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwJXokJwpEbGdrcN5Y29ycA" class="cyc_term">Path_Spatial</a> that is followed, at least in part, during the event. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvt3H_5wpEbGdrcN5Y29ycA" class="cyc_term">infoPathway_Partial</a> TRANS PATH)</code> means that part of the route of <code>TRANS</code> is spatial and follows part of <code>PATH</code>. For example, consider a transfer <code>INFOTRANS</code> in which an e-mail is sent from one PC to another, and the information content of the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvkNufpwpEbGdrcN5Y29ycA" class="cyc_term">InformationBearingThing</a> transferred is successfully transferred. Suppose <code>INFOTRANS</code> is routed along several distinct cables. If one of these cables is <code>CABLE001</code>, then <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvt3H_5wpEbGdrcN5Y29ycA" class="cyc_term">infoPathway_Partial</a> INFOTRANS CABLE001)</code> holds. See also <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv8HK45wpEbGdrcN5Y29ycA" class="cyc_term">infoPathway_Complete</a>. Note that in the example above it would be incorrect to replace <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvt3H_5wpEbGdrcN5Y29ycA" class="cyc_term">infoPathway_Partial</a> with <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv8HK45wpEbGdrcN5Y29ycA" class="cyc_term">infoPathway_Complete</a>, since the entire transfer did not occur along <code>CABLE001</code>. partial information pathway used

<code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkG55wpEbGdrcN5Y29ycA" class="cyc_term">products</a> EV OBJ)</code> means that <code>OBJ</code> is one of the intended outputs of event <code>EV</code>. For unintended outputs, see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjCXJwpEbGdrcN5Y29ycA" class="cyc_term">byProducts</a>. For a particular <code>EV</code> and <code>OBJ</code>, it will not be true that both <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkG55wpEbGdrcN5Y29ycA" class="cyc_term">products</a> EV OBJ)</code> and <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjCXJwpEbGdrcN5Y29ycA" class="cyc_term">byProducts</a> EV OBJ)</code>. product products

AnimateActivity A specialization of both <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVioQZwpEbGdrcN5Y29ycA" class="cyc_term">Action</a> (q.v.) and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvjJE4ZwpEbGdrcN5Y29ycA" class="cyc_term">Event_Localized</a>. Every instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rMdh6rlWAQdeAJcjp98P_yg" class="cyc_term">AnimateActivity</a> is a spatially-localized action, each of whose "doers" (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1HmJwpEbGdrcN5Y29ycA" class="cyc_term">doneBy</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rQ9dkLFWAQdeQE7cXOq70Qg" class="cyc_term">animateDoer</a>s) is either a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVim7ZwpEbGdrcN5Y29ycA" class="cyc_term">BiologicalLivingObject</a> or a group of BLOs (i.e. a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjmoJwpEbGdrcN5Y29ycA" class="cyc_term">Group</a> all of whose members are BLOs). Specializations of this collection include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViNqpwpEbGdrcN5Y29ycA" class="cyc_term">AnimalActivity</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkCt5wpEbGdrcN5Y29ycA" class="cyc_term">BiologicalEvent</a>, and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjzlpwpEbGdrcN5Y29ycA" class="cyc_term">PhysiologicalProcess</a>. animate activity

movement from one place to another A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv4GokJwpEbGdrcN5Y29ycA" class="cyc_term">Translocation</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOcJwpEbGdrcN5Y29ycA" class="cyc_term">Movement_TranslationEvent</a> is an event in which an object (an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi255wpEbGdrcN5Y29ycA" class="cyc_term">SomethingExisting</a>) moves some distance (so that at some point in the event, the object's center of mass changes location with respect to the relevant frame of reference). The moving object need not move completely out of its original spatial extent; for example, a building moving one foot to the left undergoes a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOcJwpEbGdrcN5Y29ycA" class="cyc_term">Movement_TranslationEvent</a>. Instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOcJwpEbGdrcN5Y29ycA" class="cyc_term">Movement_TranslationEvent</a> include events in which the movement ends in the same place it started from (e.g. one lap of a race car around the Indianapolis race track, or a trip to the grocery store and back). In such cases (all of which are instances of the specialization <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV5EZJwpEbGdrcN5Y29ycA" class="cyc_term">Translation_NoLocationChange</a>), the to and from locations of the movement (see the predicates <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjXepwpEbGdrcN5Y29ycA" class="cyc_term">toLocation</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjiI5wpEbGdrcN5Y29ycA" class="cyc_term">fromLocation</a>) are identical. In other cases of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOcJwpEbGdrcN5Y29ycA" class="cyc_term">Movement_TranslationEvent</a> (e.g. the movement of the baseball during a home run hit by Roger Maris), the to and from locations are different; in these cases, the movement events are also instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV-BF5wpEbGdrcN5Y29ycA" class="cyc_term">Translation_LocationChange</a> (q.v.). Movement-TranslationEvent

properSubEvents Proper Sub Events A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rBCj1OqKRQdeRRuR9K1A5lQ" class="cyc_term">properSubSituations</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViQmZwpEbGdrcN5Y29ycA" class="cyc_term">subEvents</a> (qq.v.). This predicate relates events to further events which are their proper sub-events. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rMfpoxnOxQdiInZcva6xBew" class="cyc_term">properSubEvents</a> EVENT SUBEVENT)</code> means that the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a> <code>SUBEVENT</code> is a part of the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a> <code>EVENT</code>, a complete description of <code>EVENT</code> would have to involve a description of <code>SUBEVENT</code>, and <code>SUBEVENT</code> is not identical to <code>EVENT</code> itself. For example, an event in which a car is being parallel-parked might be an event in which a person turning a steering wheel is a proper sub-event. See also <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rgq1joHO1QdicgbqxtOORbw" class="cyc_term">properSubEventTypes</a>.

social event A specialization of both <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVieP5wpEbGdrcN5Y29ycA" class="cyc_term">PurposefulAction</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViNJ5wpEbGdrcN5Y29ycA" class="cyc_term">CompositePhysicalAndMentalEvent</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViPO5wpEbGdrcN5Y29ycA" class="cyc_term">SocialOccurrence</a> is an action in which two or more agents take part. In many cases, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViPO5wpEbGdrcN5Y29ycA" class="cyc_term">SocialOccurrence</a>s involve communication among the participating agents. Some instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViPO5wpEbGdrcN5Y29ycA" class="cyc_term">SocialOccurrence</a> have very elaborate role structures (e.g. a typical lawsuit), while others have fairly simple role structures (e.g. greeting a colleague at work). SocialOccurrence

CommunicationAct-Single single communication act A collection of information transfer events; a specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViexZwpEbGdrcN5Y29ycA" class="cyc_term">Communicating</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVieg5wpEbGdrcN5Y29ycA" class="cyc_term">CommunicationAct_Single</a> is a single-source transmission of information from one sender (see the predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViPLZwpEbGdrcN5Y29ycA" class="cyc_term">senderOfInfo</a>) to one or more recipients (see the predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVqYY5wpEbGdrcN5Y29ycA" class="cyc_term">recipientOfInfo</a>). Every instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVieg5wpEbGdrcN5Y29ycA" class="cyc_term">CommunicationAct_Single</a> has a transmission sub-event (which is an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvXDRVpwpEbGdrcN5Y29ycA" class="cyc_term">IBTGeneration</a>) and one or more reception sub-events (which are instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjWH5wpEbGdrcN5Y29ycA" class="cyc_term">AccessingAnIBT</a>). An instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVieg5wpEbGdrcN5Y29ycA" class="cyc_term">CommunicationAct_Single</a> starts when its transmission sub-event starts and ends when its accessing sub-event(s) end.

MovementProcess A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEAZwpEbGdrcN5Y29ycA" class="cyc_term">MovementEvent</a> and an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVitN5wpEbGdrcN5Y29ycA" class="cyc_term">TemporalStuffType</a>. Each instance MOTION of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViQzZwpEbGdrcN5Y29ycA" class="cyc_term">MovementProcess</a> is a movement event that can be considered as a continuous motion. That is, (i) motion happens without interruption throughout MOTION and thus (ii) every time-slice of MOTION is itself a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViQzZwpEbGdrcN5Y29ycA" class="cyc_term">MovementProcess</a>. movement

change of location A collection of translational motion events; thus a subcollection of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOcJwpEbGdrcN5Y29ycA" class="cyc_term">Movement_TranslationEvent</a>. In each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV-BF5wpEbGdrcN5Y29ycA" class="cyc_term">Translation_LocationChange</a>, the moving object (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a>) ends up in a different place than it started from: the destination (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjXepwpEbGdrcN5Y29ycA" class="cyc_term">toLocation</a>) is not the same as the origin (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjiI5wpEbGdrcN5Y29ycA" class="cyc_term">fromLocation</a>). Thus, a round-trip travel event (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwQruB5wpEbGdrcN5Y29ycA" class="cyc_term">Translation_RoundTrip</a>) is _not_ an instance of this collection. Cf. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV5EZJwpEbGdrcN5Y29ycA" class="cyc_term">Translation_NoLocationChange</a>. Translation-LocationChange

affected object objectActedOn The predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi65pwpEbGdrcN5Y29ycA" class="cyc_term">objectActedOn</a> is used to relate an event to any object significantly affected in that event. The entity or entities in question must exist before the event, but may be either destroyed in the event (see the more specific predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWWNUJwpEbGdrcN5Y29ycA" class="cyc_term">inputsDestroyed</a>), or merely affected by it (for example, see the more specific predicates <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVifsJwpEbGdrcN5Y29ycA" class="cyc_term">damages</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkIMZwpEbGdrcN5Y29ycA" class="cyc_term">objectOfStateChange</a>). <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi65pwpEbGdrcN5Y29ycA" class="cyc_term">objectActedOn</a> EVENT OBJECT)</code> means that <code>OBJECT</code> is altered or affected in <code>EVENT</code>, and the change that <code>OBJECT</code> undergoes is central or focal to understanding <code>EVENT</code>. Thus, scissors are not an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi65pwpEbGdrcN5Y29ycA" class="cyc_term">objectActedOn</a> in a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViw4JwpEbGdrcN5Y29ycA" class="cyc_term">HairCuttingEvent</a>. The focal change in a haircut is hair getting shorter; thus, hair is a legitimate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi65pwpEbGdrcN5Y29ycA" class="cyc_term">objectActedOn</a> in a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViw4JwpEbGdrcN5Y29ycA" class="cyc_term">HairCuttingEvent</a>. The almost microscopic dulling that scissors undergo in a single haircut is a comparatively insignificant change with respect to a single haircut, considered as a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViw4JwpEbGdrcN5Y29ycA" class="cyc_term">HairCuttingEvent</a>.

The predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjK3JwpEbGdrcN5Y29ycA" class="cyc_term">stuffUsed</a> relates an event to some tangible substance which facilitates that event. (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjK3JwpEbGdrcN5Y29ycA" class="cyc_term">stuffUsed</a> EVENT STUFF) means that STUFF is a portion of an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVny6pwpEbGdrcN5Y29ycA" class="cyc_term">ExistingStuffType</a> which plays an instrumental role in EVENT. STUFF may or may not be consumed in the course of EVENT. Examples: portions of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjAHZwpEbGdrcN5Y29ycA" class="cyc_term">Water</a> are <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjK3JwpEbGdrcN5Y29ycA" class="cyc_term">stuffUsed</a> in instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViyG5wpEbGdrcN5Y29ycA" class="cyc_term">WashingDishes</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj3q5wpEbGdrcN5Y29ycA" class="cyc_term">WashingHair</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViz35wpEbGdrcN5Y29ycA" class="cyc_term">WashingClothesInAMachine</a>, etc.; portions of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjZJJwpEbGdrcN5Y29ycA" class="cyc_term">EdibleOil</a> are <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjK3JwpEbGdrcN5Y29ycA" class="cyc_term">stuffUsed</a> in some instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi665wpEbGdrcN5Y29ycA" class="cyc_term">Frying</a> food and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViH6ZwpEbGdrcN5Y29ycA" class="cyc_term">BakingBread</a>. stuffUsed stuff used

object of state change The predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkIMZwpEbGdrcN5Y29ycA" class="cyc_term">objectOfStateChange</a> is used to identify an object undergoing a change of state in an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWESd5wpEbGdrcN5Y29ycA" class="cyc_term">IntrinsicStateChangeEvent</a>. (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkIMZwpEbGdrcN5Y29ycA" class="cyc_term">objectOfStateChange</a> EVENT OBJECT) means that the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj27ZwpEbGdrcN5Y29ycA" class="cyc_term">PartiallyTangible</a> OBJECT undergoes some kind of intrinsic change of state (such as a change in one of its physical properties) in the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWESd5wpEbGdrcN5Y29ycA" class="cyc_term">IntrinsicStateChangeEvent</a> EVENT. OBJECT exists before EVENT, is directly involved in EVENT, and persists after EVENT (accordingly, this predicate has as <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVtJUZwpEbGdrcN5Y29ycA" class="cyc_term">genlPreds</a> both <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWDKWZwpEbGdrcN5Y29ycA" class="cyc_term">preActors</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV5SppwpEbGdrcN5Y29ycA" class="cyc_term">postActors</a>). The change which OBJECT undergoes is internal or intrinsic; this predicate is not used for extrinsic changes, such as changes in location, orientation, ownership, or status. Note that if OBJECT were destroyed by EVENT and went out of existence in the course of EVENT, then the right predicate to use would be <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWWNUJwpEbGdrcN5Y29ycA" class="cyc_term">inputsDestroyed</a>, rather than <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkIMZwpEbGdrcN5Y29ycA" class="cyc_term">objectOfStateChange</a>. objectOfStateChange

periodic translation Translation-Periodic A specialization of both <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOcJwpEbGdrcN5Y29ycA" class="cyc_term">Movement_TranslationEvent</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWWHKZwpEbGdrcN5Y29ycA" class="cyc_term">Movement_Periodic</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV4dQpwpEbGdrcN5Y29ycA" class="cyc_term">Translation_Periodic</a> is a translational movement in which the moving object returns to a certain location repeatedly, and at more or less regular time intervals. Instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV4dQpwpEbGdrcN5Y29ycA" class="cyc_term">Translation_Periodic</a> include a ball bouncing in place and a planet revolving around a star. Note that a planet rotating on its axis or a top spinning in place would not count as an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV4dQpwpEbGdrcN5Y29ycA" class="cyc_term">Translation_Periodic</a>, since these movements, although periodic, are rotations rather than translations.

A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvjJE4ZwpEbGdrcN5Y29ycA" class="cyc_term">Event_Localized</a>. During each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWdRSZwpEbGdrcN5Y29ycA" class="cyc_term">CreationOrDestructionEvent</a>, one or more instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi255wpEbGdrcN5Y29ycA" class="cyc_term">SomethingExisting</a> (q.v.) come into or go out of existence. Specializations of this collection include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjeiZwpEbGdrcN5Y29ycA" class="cyc_term">CreationEvent</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj5IJwpEbGdrcN5Y29ycA" class="cyc_term">DestructionEvent</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjhdZwpEbGdrcN5Y29ycA" class="cyc_term">Manufacturing</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj-OJwpEbGdrcN5Y29ycA" class="cyc_term">MakingSomething</a>, and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVisLpwpEbGdrcN5Y29ycA" class="cyc_term">KillingByOrganism</a>. CreationOrDestructionEvent creation or destruction event

bodily doer An <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAKZwpEbGdrcN5Y29ycA" class="cyc_term">ActorSlot</a> and a specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rQ9dkLFWAQdeQE7cXOq70Qg" class="cyc_term">animateDoer</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV5E85wpEbGdrcN5Y29ycA" class="cyc_term">nonDeliberateActors</a> (qq.v.). The predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV_GH5wpEbGdrcN5Y29ycA" class="cyc_term">bodilyDoer</a> relates a given physical event to any organism that is a non-deliberate "doer" of the event (i.e. the organism acts without conscious intention or volition). (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV_GH5wpEbGdrcN5Y29ycA" class="cyc_term">bodilyDoer</a> EVENT DOER) means that DOER does EVENT (which entails that DOER is not merely subjected to EVENT by external forces), but does it non-deliberately. Note that for certain kinds of actions (e.g. physical growth, peristalsis, and reflex actions) organisms are always merely <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV_GH5wpEbGdrcN5Y29ycA" class="cyc_term">bodilyDoer</a>s; for certain other actions (e.g. breathing, flinching, and shouting) an organism commonly acts as a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV_GH5wpEbGdrcN5Y29ycA" class="cyc_term">bodilyDoer</a>, but sometimes acts instead as a deliberate performer (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVipYpwpEbGdrcN5Y29ycA" class="cyc_term">performedBy</a>). Note also that an organism that dies of natural causes is the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV_GH5wpEbGdrcN5Y29ycA" class="cyc_term">bodilyDoer</a> of that event, because of the internal processes the body does during its <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkJU5wpEbGdrcN5Y29ycA" class="cyc_term">Dying</a>. And in certain <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwQw4WZwpEbGdrcN5Y29ycA" class="cyc_term">PhysiologicalCondition</a>s, including an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwQwYVpwpEbGdrcN5Y29ycA" class="cyc_term">AilmentCondition</a> (e.g. diabetes) or a healing process, organisms are considered to be <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV_GH5wpEbGdrcN5Y29ycA" class="cyc_term">bodilyDoer</a>s because their own bodily processes are creating or sustaining those conditions. An organism killed by an external agent, however, is just a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjQK5wpEbGdrcN5Y29ycA" class="cyc_term">bodilyActedOn</a> (q.v.) actor in that event; thus instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVisLpwpEbGdrcN5Y29ycA" class="cyc_term">KillingByOrganism</a> should use <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjQK5wpEbGdrcN5Y29ycA" class="cyc_term">bodilyActedOn</a> to describe the organism killed. bodilyDoer

directing agent An instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAKZwpEbGdrcN5Y29ycA" class="cyc_term">ActorSlot</a> (q.v.) that is a specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1fHJwpEbGdrcN5Y29ycA" class="cyc_term">deliberateActors</a>. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViWkJwpEbGdrcN5Y29ycA" class="cyc_term">directingAgent</a> EVENT DIRECTOR)</code> means that <code>DIRECTOR</code> deliberately controls or directs <code>EVENT</code>, typically by controlling other participants in <code>EVENT</code> (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv1aZ05wpEbGdrcN5Y29ycA" class="cyc_term">controls</a>). <code>AGENT</code> might or might not perform <code>EVENT</code> directly. If an agent other than <code>DIRECTOR</code> performs (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVipYpwpEbGdrcN5Y29ycA" class="cyc_term">performedBy</a>) <code>EVENT</code>, then that performer's actions in <code>EVENT</code> are controlled by at least one of <code>EVENT</code>'s directing agents. (In many cases, of course, <code>EVENT</code> will have only one director.) Non-performing directors typically control the actual performers by communicating instructions (or orders, commands, etc.) to them. For example, (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViWkJwpEbGdrcN5Y29ycA" class="cyc_term">directingAgent</a> PSOBicentennialConcertOfBeethovensNinth WilliamSteinberg) holds, because Steinberg was the conductor of that concert; he directed the many other musicians who performed in that event. Other examples are (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViWkJwpEbGdrcN5Y29ycA" class="cyc_term">directingAgent</a> MassacreAtMyLai LtWilliamCalley) and (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViWkJwpEbGdrcN5Y29ycA" class="cyc_term">directingAgent</a> TateLaBiancaMurders CharlesManson). directingAgent

inputs An <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAKZwpEbGdrcN5Y29ycA" class="cyc_term">ActorSlot</a> and a specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi65pwpEbGdrcN5Y29ycA" class="cyc_term">objectActedOn</a> that relates a given event to an object or material that is used in that event and thereby either "used up" (i.e. destroyed) or incorporated into another object. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi3DZwpEbGdrcN5Y29ycA" class="cyc_term">inputs</a> EVENT OBJECT)</code> means that <code>OBJECT</code> is a pre-existing participant in (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWDKWZwpEbGdrcN5Y29ycA" class="cyc_term">preActors</a>) the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWdRSZwpEbGdrcN5Y29ycA" class="cyc_term">CreationOrDestructionEvent</a> <code>EVENT</code> which, during and due to <code>EVENT</code>, is either destroyed (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWWNUJwpEbGdrcN5Y29ycA" class="cyc_term">inputsDestroyed</a>) or incorporated into a new entity (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWPtrJwpEbGdrcN5Y29ycA" class="cyc_term">inputsCommitted</a>). For example, the pigments used to paint the Mona Lisa were <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi3DZwpEbGdrcN5Y29ycA" class="cyc_term">inputs</a> to Leonardo's painting process; however, his brushes were not <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi3DZwpEbGdrcN5Y29ycA" class="cyc_term">inputs</a>, even though they were changed a little by it. In general, in instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjhdZwpEbGdrcN5Y29ycA" class="cyc_term">Manufacturing</a>, materials or objects are inputs if they find their way into the product manufactured or if they are destroyed in the manufacturing process (e.g. the coke used in manufacturing steel). input

A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvn69UJwpEbGdrcN5Y29ycA" class="cyc_term">informationTerminal</a> (q.v.) that is used to indicate the source of information for a particular <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVifB5wpEbGdrcN5Y29ycA" class="cyc_term">InformationTransferEvent</a> (q.v.). <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV5PA5wpEbGdrcN5Y29ycA" class="cyc_term">informationOrigin</a> TRANSFER ORIGIN)</code> means that the information being transferred in <code>TRANSFER</code> comes from <code>ORIGIN</code>. <code>ORIGIN</code> is either an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvkNufpwpEbGdrcN5Y29ycA" class="cyc_term">InformationBearingThing</a> or an agent. Note that if <code>ORIGIN</code> still exists after the ending of <code>TRANSFER</code>, it presumably also still contains the information that was transferred. informationOrigin Information Origin

anatomical part involved actorPartsInvolved (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi20pwpEbGdrcN5Y29ycA" class="cyc_term">actorPartsInvolved</a> ACT PART) means that PART is one of the parts (see the predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjufpwpEbGdrcN5Y29ycA" class="cyc_term">anatomicalParts</a>) of an organism that is playing an active role (see the predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1HmJwpEbGdrcN5Y29ycA" class="cyc_term">doneBy</a> and its specializations) in the event ACT, and, moreover, that PART is somehow involved in the event ACT. Some examples of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi20pwpEbGdrcN5Y29ycA" class="cyc_term">actorPartsInvolved</a> include: the eyes of someone who is sneezing (or crying); the left foot of someone playing in a football game; the right hand of someone who is shaking hands; the claws of a cat who is scratching someone. As a negative example, consider a person's hair when that person is getting a haircut. The hair is not an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi20pwpEbGdrcN5Y29ycA" class="cyc_term">actorPartsInvolved</a>, because the person is passive in that event; it is, however, an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi1S5wpEbGdrcN5Y29ycA" class="cyc_term">actorPartsAffected</a> (q.v.) in that event.

The predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwQ_BQpwpEbGdrcN5Y29ycA" class="cyc_term">affectedAgent</a> relates a particular event to those agents who are affected by it. (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwQ_BQpwpEbGdrcN5Y29ycA" class="cyc_term">affectedAgent</a> EVT AGT) means that AGT is harmed, benefitted, or otherwise acted upon in or as a result of EVT. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwQ_BQpwpEbGdrcN5Y29ycA" class="cyc_term">affectedAgent</a> is not an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAKZwpEbGdrcN5Y29ycA" class="cyc_term">ActorSlot</a> because it is not a specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjFpZwpEbGdrcN5Y29ycA" class="cyc_term">actors</a> -- if an individual is affected in or as a result of an event, that individual need not participate in the event; indeed, that individual need not temporally intersect the event. affectedAgent affected agent

performedBy performer An <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvrseL5wpEbGdrcN5Y29ycA" class="cyc_term">AgentiveRole</a> (q.v.) predicate that relates an action (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVioQZwpEbGdrcN5Y29ycA" class="cyc_term">Action</a>) to an agent (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAB5wpEbGdrcN5Y29ycA" class="cyc_term">Agent_PartiallyTangible</a>) who performs it deliberately, i.e. intentionally and volitionally. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVipYpwpEbGdrcN5Y29ycA" class="cyc_term">performedBy</a> ACT DOER)</code> means that <code>DOER</code> deliberately does <code>ACT</code>. For example, (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVipYpwpEbGdrcN5Y29ycA" class="cyc_term">performedBy</a> #$AssassinationOfPresidentLincoln <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwQCgL5wpEbGdrcN5Y29ycA" class="cyc_term">JohnWilkesBooth</a>) holds. Note that an action can have multiple deliberate performers. See also the generalizations <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1fHJwpEbGdrcN5Y29ycA" class="cyc_term">deliberateActors</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1HmJwpEbGdrcN5Y29ycA" class="cyc_term">doneBy</a>.

A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEAZwpEbGdrcN5Y29ycA" class="cyc_term">MovementEvent</a>. In each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjLCpwpEbGdrcN5Y29ycA" class="cyc_term">Movement_Rotation</a> the most salient moving object (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvXxi65wpEbGdrcN5Y29ycA" class="cyc_term">primaryObjectMoving</a>) rotates (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwHI-X5wpEbGdrcN5Y29ycA" class="cyc_term">objectRotating</a>). That is, the object rotates about an axis (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvhWXX5wpEbGdrcN5Y29ycA" class="cyc_term">axisOfRotation</a>) that spatially intersects it (or goes through a hole in it). Examples include the daily rotation of the Earth on its axis and the rotation of a clock hand about its fastened end. A non-example is the orbiting of the Earth around the sun, as the axis of the orbit does not spatially intersect the Earth. Movement-Rotation rotation

transportee transportees The predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViulJwpEbGdrcN5Y29ycA" class="cyc_term">transportees</a> relates a translational motion event to the object(s) transported in that event. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViulJwpEbGdrcN5Y29ycA" class="cyc_term">transportees</a> MOVE OBJ)</code> means that some conveyance (see the predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwPqxbJwpEbGdrcN5Y29ycA" class="cyc_term">conveyor_Generic</a>) transports <code>OBJ</code> in <code>MOVE</code>. The conveyance in question can either move along with <code>OBJ</code> in <code>MOVE</code> or remain stationary during <code>MOVE</code>. The conveyance in question is separate from <code>OBJ</code> (that is, <code>OBJ</code> is not a part of the conveyance).

This predicate relates a particular creation or destruction event to any of its "outputs". <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViYA5wpEbGdrcN5Y29ycA" class="cyc_term">outputs</a> EVENT OBJECT)</code> means that <code>OBJECT</code> is an output of <code>EVENT</code>. That is, <code>OBJECT</code> is either created/produced as a result of <code>EVENT</code> (see the specializations <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWStbZwpEbGdrcN5Y29ycA" class="cyc_term">outputsCreated</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkG55wpEbGdrcN5Y29ycA" class="cyc_term">products</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjCXJwpEbGdrcN5Y29ycA" class="cyc_term">byProducts</a>) or something left after another thing was destroyed in <code>EVENT</code> (see the specialization <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWTgkpwpEbGdrcN5Y29ycA" class="cyc_term">outputsRemaining</a>). For example, silicon chips are both <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWStbZwpEbGdrcN5Y29ycA" class="cyc_term">outputsCreated</a> in and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkG55wpEbGdrcN5Y29ycA" class="cyc_term">products</a> of a chip manufacturing process, while a hunk of scrap metal is an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWTgkpwpEbGdrcN5Y29ycA" class="cyc_term">outputsRemaining</a> after a car is put through a crusher. When appropriate, instead of using <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViYA5wpEbGdrcN5Y29ycA" class="cyc_term">outputs</a>, use one of its specializations (of which those mentioned above are the nearest). output outputs

intended recipient of communication communicationTarget The predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVwuhZwpEbGdrcN5Y29ycA" class="cyc_term">communicationTarget</a> is used to indicate an intended recipient in a communication act. (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVwuhZwpEbGdrcN5Y29ycA" class="cyc_term">communicationTarget</a> COMM AGENT) means that the agent who originates the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVieg5wpEbGdrcN5Y29ycA" class="cyc_term">CommunicationAct_Single</a> COMM intends the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVqYY5wpEbGdrcN5Y29ycA" class="cyc_term">recipientOfInfo</a> to be AGENT. Note that AGENT may or may not receive the information contained in COMM. To indicate both that AGENT is an intended recipient of COMM, and that AGENT actually receives the information contained in COMM, use the more specialized predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv7XiW5wpEbGdrcN5Y29ycA" class="cyc_term">recipientOfInfo_Intended</a>.

An <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAKZwpEbGdrcN5Y29ycA" class="cyc_term">ActorSlot</a> (q.v.) and a specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjFpZwpEbGdrcN5Y29ycA" class="cyc_term">actors</a> with respect to social events. (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAFJwpEbGdrcN5Y29ycA" class="cyc_term">socialParticipants</a> SOCIAL-EVENT AGENT) means that the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvsaaeJwpEbGdrcN5Y29ycA" class="cyc_term">Agent_Generic</a> AGENT participates --- in some social role --- in the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViPO5wpEbGdrcN5Y29ycA" class="cyc_term">SocialOccurrence</a> SOCIAL-EVENT. In every culture there is a wide variety of such relations of social participation, thus <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAFJwpEbGdrcN5Y29ycA" class="cyc_term">socialParticipants</a> has many specializations. Some <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViPO5wpEbGdrcN5Y29ycA" class="cyc_term">SocialOccurrence</a>s have very elaborate role structures (e.g. a lawsuit in 1990's America), and some are fairly simple (e.g. rudely bumping into someone). Some example specializations are <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjs1ZwpEbGdrcN5Y29ycA" class="cyc_term">bride</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjRYpwpEbGdrcN5Y29ycA" class="cyc_term">interviewee</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwMtbEJwpEbGdrcN5Y29ycA" class="cyc_term">tourParticipants</a>. Note that AGENT's participation in SOCIAL-EVENT need not be deliberate or intentional: one can sleep through a meeting and a newborn baby can attend a picnic. For social participation that is expressly deliberate, see the specialization <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rviC0JpwpEbGdrcN5Y29ycA" class="cyc_term">deliberateSocialParticipants</a>. social participant socialParticipants

SingleDoerAction action with only one performer A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVioQZwpEbGdrcN5Y29ycA" class="cyc_term">Action</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1IRJwpEbGdrcN5Y29ycA" class="cyc_term">SingleDoerAction</a> is an action which can have only one "doer" (see the predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1HmJwpEbGdrcN5Y29ycA" class="cyc_term">doneBy</a>). Such actions may be intentional, but they need not be. Most bodily functions (e.g., the instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViYhJwpEbGdrcN5Y29ycA" class="cyc_term">Heartbeating</a> or <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjPypwpEbGdrcN5Y29ycA" class="cyc_term">Bleeding_TheAction</a>) belong to specializations of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1IRJwpEbGdrcN5Y29ycA" class="cyc_term">SingleDoerAction</a>, because the only doer of a normal bodily function is the body of a single agent. In order for a type of action (i.e., a specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVioQZwpEbGdrcN5Y29ycA" class="cyc_term">Action</a>) to be a specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1IRJwpEbGdrcN5Y29ycA" class="cyc_term">SingleDoerAction</a>, it must be inconsistent to assert, for any instance <code>ACT</code> of that type of action, both <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1HmJwpEbGdrcN5Y29ycA" class="cyc_term">doneBy</a> ACT X)</code> and <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1HmJwpEbGdrcN5Y29ycA" class="cyc_term">doneBy</a> ACT Y)</code>, where <code>X</code> and <code>Y</code> are different. Notable specializations of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1IRJwpEbGdrcN5Y29ycA" class="cyc_term">SingleDoerAction</a> include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjSm5wpEbGdrcN5Y29ycA" class="cyc_term">Sleeping</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkJU5wpEbGdrcN5Y29ycA" class="cyc_term">Dying</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjXfZwpEbGdrcN5Y29ycA" class="cyc_term">AnimalWalkingProcess</a>, and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViMp5wpEbGdrcN5Y29ycA" class="cyc_term">WritingByHand</a>.

The most general instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAKZwpEbGdrcN5Y29ycA" class="cyc_term">ActorSlot</a> (q.v.): all other actor slots are specializations of this predicate. Thus <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjFpZwpEbGdrcN5Y29ycA" class="cyc_term">actors</a> is a broad relation that holds between a given event and any contemporary existing thing (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi255wpEbGdrcN5Y29ycA" class="cyc_term">SomethingExisting</a>) that is meaningfully involved in the event. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjFpZwpEbGdrcN5Y29ycA" class="cyc_term">actors</a> EVENT ACTOR)</code> means that <code>ACTOR</code> is somehow saliently (directly or indirectly) involved in <code>EVENT</code> during <code>EVENT</code>. An object's merely being cotemporal (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjWz5wpEbGdrcN5Y29ycA" class="cyc_term">cotemporal</a>) with an event is obviously not sufficient for being an actor in it, nor is participating (however centrally) in a representation or re-enactment of the event. But note that being an "actor" in the relevant sense is not restricted to things that play "active" (as opposed to passive or instrumental) roles in a given event. actors actor

(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV5E85wpEbGdrcN5Y29ycA" class="cyc_term">nonDeliberateActors</a> ACT ACTOR) means that ACTOR plays some role in the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a> ACT, but is not acting deliberately. For example, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwPzUNJwpEbGdrcN5Y29ycA" class="cyc_term">JohnKennedy</a> was a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV5E85wpEbGdrcN5Y29ycA" class="cyc_term">nonDeliberateActors</a> in his assassination, a person is a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV5E85wpEbGdrcN5Y29ycA" class="cyc_term">nonDeliberateActors</a> in his/her own autonomic bodily functioning, and Mount <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjuO5wpEbGdrcN5Y29ycA" class="cyc_term">Vesuvius_Volcano</a> was a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV5E85wpEbGdrcN5Y29ycA" class="cyc_term">nonDeliberateActors</a> in the event of its eruption that destroyed Pompeii. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV5E85wpEbGdrcN5Y29ycA" class="cyc_term">nonDeliberateActors</a> is a negative specification of the role an actor has in an event; the role of particular <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV5E85wpEbGdrcN5Y29ycA" class="cyc_term">nonDeliberateActors</a> might be further specified positively, for example, with <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjQK5wpEbGdrcN5Y29ycA" class="cyc_term">bodilyActedOn</a> or <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV_GH5wpEbGdrcN5Y29ycA" class="cyc_term">bodilyDoer</a>. non-deliberate actor nonDeliberateActors

Information Terminal This predicate is used to indicate any instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAxJwpEbGdrcN5Y29ycA" class="cyc_term">TemporalThing</a> that plays the role of either <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVipxZwpEbGdrcN5Y29ycA" class="cyc_term">informationDestination</a> or <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV5PA5wpEbGdrcN5Y29ycA" class="cyc_term">informationOrigin</a> in any instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVifB5wpEbGdrcN5Y29ycA" class="cyc_term">InformationTransferEvent</a>, i.e. plays the role of endpoint. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvn69UJwpEbGdrcN5Y29ycA" class="cyc_term">informationTerminal</a> TRANS THING)</code> means the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAxJwpEbGdrcN5Y29ycA" class="cyc_term">TemporalThing</a> <code>THING</code> was either the origin or destination of the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVifB5wpEbGdrcN5Y29ycA" class="cyc_term">InformationTransferEvent</a> <code>TRANS</code>. informationTerminal

class of concepts belonging to a shared domain ConceptTypeByDomain Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4ret7qgOKgEdmAAAACs6hfSg" class="cyc_term">ConceptTypeByDomain</a> is a collection, all of whose elements can be considered concepts which belong to some domain of knowledge. For example, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rWJzeaOKhEdmAAAACs6hfSg" class="cyc_term">FamilyRelationsConcept</a> is the collection that includes predicates, such as <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjj6ZwpEbGdrcN5Y29ycA" class="cyc_term">siblings</a> or <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjPcJwpEbGdrcN5Y29ycA" class="cyc_term">children</a>, collections, such as <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjhG5wpEbGdrcN5Y29ycA" class="cyc_term">FamilyCohabitationUnit</a>, and potentially other concepts that are part of the domain of family relationships. It is important to note that instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4ret7qgOKgEdmAAAACs6hfSg" class="cyc_term">ConceptTypeByDomain</a> are not quoted collections -- i.e., their elements are not the _terms_ used to represent the concepts, but instead are the concepts themselves. thing Thing <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViA9JwpEbGdrcN5Y29ycA" class="cyc_term">Thing</a> is the "universal collection": the collection which, by definition, contains everything there is. Every thing in the Cyc ontology -- every <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjaApwpEbGdrcN5Y29ycA" class="cyc_term">Individual</a> (of any kind), every <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvl2en5wpEbGdrcN5Y29ycA" class="cyc_term">Set_Mathematical</a>, and every <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAzJwpEbGdrcN5Y29ycA" class="cyc_term">Collection</a> -- is an instance of (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViBBJwpEbGdrcN5Y29ycA" class="cyc_term">isa</a>) <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViA9JwpEbGdrcN5Y29ycA" class="cyc_term">Thing</a>. Similarly, every collection is a subcollection of (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViBDpwpEbGdrcN5Y29ycA" class="cyc_term">genls</a>) <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViA9JwpEbGdrcN5Y29ycA" class="cyc_term">Thing</a>. Trivially, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViA9JwpEbGdrcN5Y29ycA" class="cyc_term">Thing</a> is both an instance of and a subcollection of itself, and is not a subcollection of any other collection. (Note that the above reference to "every thing in the Cyc ontology" is not meant to be limited to things actually reified in the Cyc system, but includes (e.g.) every instance -- reified or not, known or not -- of every collection recognized by Cyc.) Pretty String (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwLSVCpwpEbGdrcN5Y29ycA" class="cyc_term">prettyString</a> TERM STRING) means that STRING is the English word or expression (sequence of words) commonly used to refer to TERM. The predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwLSVCpwpEbGdrcN5Y29ycA" class="cyc_term">prettyString</a> is used by the code which generates CycL to English paraphrases, but its applicability is not restricted to this use. prettyString EventOrRoleConcept the event or role domain A <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4ret7qgOKgEdmAAAACs6hfSg" class="cyc_term">ConceptTypeByDomain</a> (q.v.). Instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r8IAy8P-fEdmAAAACs0uFOQ" class="cyc_term">EventOrRoleConcept</a> are collections and relations having to do with general kinds of events and the roles that things can play in them. Major specializations of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAA5wpEbGdrcN5Y29ycA" class="cyc_term">Role</a>, and other relations used for stating significant facts about events (such as time, place, causes, and effects) are instances of this collection. EventOrRoleConcept the event or role domain A <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4ret7qgOKgEdmAAAACs6hfSg" class="cyc_term">ConceptTypeByDomain</a> (q.v.). Instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r8IAy8P-fEdmAAAACs0uFOQ" class="cyc_term">EventOrRoleConcept</a> are collections and relations having to do with general kinds of events and the roles that things can play in them. Major specializations of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAA5wpEbGdrcN5Y29ycA" class="cyc_term">Role</a>, and other relations used for stating significant facts about events (such as time, place, causes, and effects) are instances of this collection. EventOrRoleConcept the event or role domain A <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4ret7qgOKgEdmAAAACs6hfSg" class="cyc_term">ConceptTypeByDomain</a> (q.v.). Instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r8IAy8P-fEdmAAAACs0uFOQ" class="cyc_term">EventOrRoleConcept</a> are collections and relations having to do with general kinds of events and the roles that things can play in them. Major specializations of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAA5wpEbGdrcN5Y29ycA" class="cyc_term">Role</a>, and other relations used for stating significant facts about events (such as time, place, causes, and effects) are instances of this collection.