Duplicate Identification

Use clip-level embeddings to identify near-duplicate video clips so your dataset remains compact, diverse, and efficient to train on.

Before You Start

  • Make sure you have embeddings which are written by the ClipWriterStage under ce1_embd_parquet/. For a runnable workflow, refer to the Split and Remove Duplicates Workflow. The embeddings must be in parquet files containing the columns id and embedding.
  • Verify local paths or configure S3-compatible credentials. Provide storage_options in read/write keyword arguments when reading or writing cloud paths.

How it Works

Duplicate identification operates on clip-level embeddings produced during processing:

  1. Inputs

    • Parquet batches from ClipWriterStage under ce1_embd_parquet/
    • Columns: id, embedding
  2. Outputs

    • Cluster: KMeansStage partitions embeddings and writes centroid distances (for example, cosine_dist_to_cent).
    • Pairwise: PairwiseStage computes within-cluster similarity on GPU and, for each clip, emits max_id and cosine_sim_score. Ranking controls whether to prefer outliers (“hard”) or representatives (“easy”).
    • Identify: IdentifyDuplicatesStage filters pairs with cosine_sim_score >= 1.0 - eps and writes Parquet files of duplicate ids for removal during export.

Quickstart

Use the semantic duplicate workflow with clip embeddings written to Parquet.

💡

Recommended Workflow: Determine eps First

The eps parameter is highly data-dependent and affects how many duplicates are identified. We recommend a two-step approach:

  1. Step 1: Run K-means and pairwise without duplicate identification

    • Use SemanticDeduplicationWorkflow with eps=None (or run K-means and pairwise stages individually)
    • This generates pairwise similarity scores without identifying duplicates
  2. Step 2: Inspect the similarity distribution

    • Analyze the cosine_sim_score values in the pairwise results
    • Determine an appropriate eps threshold based on your data characteristics
    • For example, if 20% of pairs have similarity ≥ 0.9, you might use eps=0.1 (since cosine_sim >= 1.0 - eps)
  3. Step 3: Run the full workflow with your chosen eps

    • Use SemanticDeduplicationWorkflow with the determined eps value
    • Or run IdentifyDuplicatesStage separately on the pairwise results

For a detailed example of this workflow with similarity analysis, see the Step-by-Step Semantic Deduplication tutorial (demonstrated on text data, but the approach applies to video clips as well).

💡

Custom Ranking with Metadata Columns

If your embedding Parquet files contain additional metadata columns (such as video quality scores, duration, resolution, or other clip attributes), you can use RankingStrategy.metadata_based() to create custom ranking methods. This allows you to prioritize which clips to keep within duplicate groups based on your specific criteria.

For example, to prefer higher quality or longer duration clips:

from nemo_curator.stages.deduplication.semantic.ranking import RankingStrategy

# Prefer clips with higher quality scores, then longer duration
ranking_strategy = RankingStrategy.metadata_based(
    metadata_cols=["quality_score", "duration"],
    ascending=[False, False],  # False = descending (higher is better)
)

# Or prefer clips closer to cluster centroid, then by quality
ranking_strategy = RankingStrategy.metadata_based(
    metadata_cols=["cosine_dist_to_cent", "quality_score"],
    ascending=[True, False],  # Closer to centroid first, then higher quality
)

The metadata columns must be present in your embedding Parquet files and will be preserved through the K-means stage. Specify these columns using the metadata_fields parameter in KMeansStage or SemanticDeduplicationWorkflow.

Parameters


Removing Duplicates

The duplicate identification stages (IdentifyDuplicatesStage or SemanticDeduplicationWorkflow with eps specified) write Parquet files containing duplicate clip IDs to the output directory (typically output_path/duplicates/). These files contain a single column id with the IDs of clips that should be removed.

It is your responsibility to exclude these duplicate IDs when exporting or persisting your final dataset. The removal process depends on how you want to persist and shard your data: