The Model-assisted labeling (MAL) workflow allows you to import computer-generated predictions (or simply annotations created outside of Labelbox) and load them as pre-labels on an asset. Using MAL for pre-labeling can be useful for speeding up the labeling process and supporting human labeling efforts.

How it works

Imported annotations will appear when the asset is opened in the Editor as long as the following conditions are met:

1. Model-assisted labeling is on

2. The imported annotations are assigned to a Data Row

3. The asset has not already been labeled in the Labelbox Editor

Currently, if a labeler skips or submits a label without making any changes first, the timer will not start and the duration time recorded will be 0 seconds. This logic may be revised in a future update.

Best practices

• Make sure the annotations are in the proper format. Use the chart below to determine whether an annotation type is supported for the data type you are labeling.

• Before you begin a new import job, make sure there are no existing MAL annotations on the Data Row. Duplicate import jobs may result in unexpected behavior.

• To override an imported annotation on a Data Row, import the annotation again using the same uuid.

Use the Python SDK to create an import job for your annotations. Choose one of the following ways to import your annotations to Labelbox

Option 1: Import via Python annotation types (recommended)

The Labelbox Python Annotation Types provide a common format for representing human and machine-generated annotations. This standard interface allows you to build one set of tools that is compatible with all of your data.

The main advantage of using Annotation types is that it converts your annotations to NDJSON format.

Here are the Python annotation types that are supported for the Model-assisted labeling workflow.

Option 2: Import via NDJSON

Your file should be in newline delimited (NDJSON) format. This means that each newline in your NDJSON file should be the entirety of a JSON object.

Create your NDJSON file

Import your NDJSON file