Each Event is a substory, therefore, to the overall flow of the storyworld. An Event will always have these three components. So the reader is assured of finding them in a HistoryBook search. Next come the secondary objects. They are only used if the Event is complicated enough to require them.
Most Events are simple enough that they only contain the core information.
Sometimes, however, an Event is more complicated and requires additional information. In normal English we handle these extras with indirect objects or prepositional phrases, but the Erasmatron can't handle such complexity, so instead we have provided secondary objects for such problems. There are two slots available for secondary objects under each data type for each Event. Thus, in our example, the hat would be stored in a secondary object called ThingObject1. The answer is, into ActorObject1.