To answer the need for a workflow representing a sequence of data transformations, a high-level process ontology was defined, denoted Pipeline Patterns (PP) ontology. Every concept is generically a Data (class from EDAM), which can be further specified as an Entry (P:00002) or an Exit (P:00009). All Entries can be subjected to an Operation (class from EDAM) producing an Intermediate (P:00010). An Intermediate has a TemporalEntity associated to represent its time of creation. Some Entries are specifically of the type Exit, meaning that they will represent concepts that exit the current category and be passed to the next one on the workflow. Additionally, in order to permit the treatment of a set of objects as a single entity, this high-level ontology considers the concept of List (P:00004) and more specifically an Aggregate (P:00005), containing a set of Data or Entry, respectively. The concept Intermediate is an Entry, allowing for the successive application of an operation to an Element. This is particularly useful in the case of the application of sequential set of operations.