Edit on Github

Concept Architecture

Anything in Grakn, whether a concept type or a data instance, is a Concept. The diagram below, illustrates how the Concept superclass is inherited by its direct and indirect descendants.

Concept Hierarchy

Type refers to a Concept Type as defined in the schema.

Thing refers to an instance of data that is an instantiation of a Concept Type.

Rule refers to a Graql Rule.

[Important] The methods called on Concepts are bound to the [transaction](../client-api/overview#transaction) that was used to retrieve the concept initially. As soon as the transaction in question is closed, methods can no longer be called on the retrieved Concepts. To continue using the Concept API on a concept, we must retrieve that concept again with a newly created transaction.

In the sections that follow, we learn about the methods available on Concept, Type, EntityType, AttributeType, RelationType, Thing, Attribute, Relation and Rule.