Customizing project interface

Labeling job types

Labeling (or annotation) jobs are labeling tasks which are associated with specific tools or input types.
For example, each one of these can be considered a Kili labeling job:

• Classification task with a multi choice dropdown input type
• Object detection task with the polygon tool
• Named entities recognition task

Kili jobs may contain nested subjobs, for example:

• Classification tasks with nested conditional questions
• Object detection tasks with nested transcription containing additional details

Some jobs types may be interdependent. For example, available relations in a named entities relation job will depend on how classes were defined in a named entities recognition job.

Additionally, each job can be either required or optional.

Kili provides the following machine learning job types:

• Classification
• Object/Entity Detection
• Object/Entity Relation
• Transcription

Availability of specific job types depends on your project asset type:

Available labeling job types per asset type

📘

Additionally, in transcription jobs, you can impose limits on the allowed input types. For example, allowing only numbers or dates.

Customizing your interface

You can customize your interface through the UI-based interface builder or through JSON settings.

In PDF projects where different pages may represent different document types, transcription and classification tasks can now be defined once and set to repeat on every page of your document. Currently, this can only be configured through the JSON interface.

Other customizations that can only be done using the JSON interface:

• Editing label metadata
• Customizing tagging colors

For details, refer to Customizing the interface through JSON settings.

Learn more

For a list of best practices, refer to Best practices for ontology design.