Entity Type
An entity type describes a class of entities with the same set of properties[1]. For example, every person has a name and a birthday. Hence person is an entity type.
An entity can have one or more entity types.
Entity types can be organized in a hierarchy. An "Employee" is a "Person". The "is a"-relationship between entity types describes that an employee can have all the attributes of a person.
Entity Types can also build a graph. If you specify the types of values for relational properties. For example, a person lives at a location.
Formal entity types can use a controlled vocabulary [2] to describe entities. For example, schema.org describes a set of entity types for use in linked data[3]. The formal description of entity types allows combining entities from different sources.
Entity types also allow the verification or corroboration of data. For example, if "John Doe" has schema.org markup on five websites, and three of the websites agree on a birthday, I can recognize this as a fact[4] of the entity. As the birthday property helps to distinguish two people, I can assume that if the other two websites agree on another birthday, then they might refer to a different person with the same name.
Footnotes
A property is a specific attribute of an entity. A property describes an entity by its value. ↩︎
A controlled vocabulary is a list of words to tag units of information in a text or document. Controlled vocabularies can be used for information retrieval. ↩︎
Linked Data is structured data that is interlinked with other data. With Linked Data structured information can be combined from different sources. ↩︎
A fact is a thing that is known or proved to be true. In knowledge graphs where information is gathered automatically, it is better to assume the information is likely to be true or has been classified as true. ↩︎