# Terminology

| Term             | Description                                                                                                                                                                                              |
| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **`Project`**    | A project is a unique labeling pipeline within which you define annotation specifications and create labeling jobs.                                                                                      |
| **`Job`**        | A job represents a unit of data to be labeled. As an example, For each image or video you want to label, you can create a separate job. An annotator can work on one job at a time.                      |
| **`Batch`**      | A batch is a collection of jobs. We recommend using batches to group datasets you use internally, or to group jobs which are part of a weekly submission.                                                |
| **`Workflow`**   | A workflow is an interactive visual representation of your labeling pipeline. When you create jobs, they move into a workflow and *flow* through the steps in the workflow till they reach the end step. |
| **`Attachment`** | An attachment is any image, PNG, PCD or JSON file associated with a job. These can be the images you want to label, or they can be the JSON file in which you fetch results.                             |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://annotationdocs.telusinternational.com/terminology.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
