Primary competition visual

Dis-Chem Product Data Enrichment Challenge

$5 000 USD
28 days left
Computer Vision
Large Language Models
Natural Language Processing
Retrieval-Augmented Generation (RAG)
160 joined
50 active
Starti
13 Nov 26
Closei
13 Dec 26
Reveali
29 Jan 27
About

This challenge uses retail product records from several product groups. The information in each record varies. Some records have detailed source text, while others have missing or masked values.

Your task is to enrich each record in Test_Masked.csv with accurate, useful product content in the ten output fields defined in ``submission_format.json``. The aim is to create clear product information that describes the exact item. This is not a request to fill every field. Every value should be supported by the supplied information or reliable evidence allowed by the content guide.

Start by confirming the product identity from its name, brand, category, descriptions, and specifications. Pay close attention to pack size, flavour, shade, weight, dimensions, and units. Similar products can differ in important ways, so do not transfer a detail from another item unless you can confirm it applies to the exact product.

Use unlabelled_data.csv to understand the catalogue and develop an approach that works across products. It has no target answers and should not be treated as a verified answer source for a test record.

Treat product identifiers as text. Preserve every record_id exactly and copy it into article_id in your submission.

Some test inputs contain missing or masked information. If a detail cannot be verified, leave its output cell blank. If a field does not apply, follow do_not_predict_fields and leave its output cell blank. If sources conflict, do not choose a value without supporting evidence. Use submission_format.json for the required columns and empty value shapes.

Phase 1 Constraints

  • End to end inference time: 3 hours maximum
  • All in inference cost: US$20 maximum
  • GPU memory: One GPU with at most 24 GB VRAM
  • Retries: At most one retry for a failed call, included in the time and cost caps
Files
Description
Files
This file contains 13,864 product records with source information and no expected output labels. The product descriptions and specifications are not masked. Use these records to understand the catalogue and develop an approach that works across products. This file is not a submission file.
This file contains 1,157 records for which you should prepare product content. Some source fields are blank or contain the marker [MASKED]. Keep each record_id unchanged and use it as the corresponding article_id in your submission. The do_not_predict_fields column contains a JSON array of output field names that do not apply to that product. Leave each corresponding submission cell blank. A blank cell is interpreted using that field’s empty value in submission_format.json. For example, a list field becomes [], while an object field uses its defined keys with empty values. Do not enter text such as N/A.
This file contains 14 example product records. It shows the input format used for the test records.
This file contains the expected structured outputs for the 14 records in template_input.csv. Match template_input.csv rows to this file using record_id and article_id. These are examples for learning the expected structure. Do not include them in your test submission.
This guide explains the content standards for product information. Use it when deciding what to include, how to handle uncertain information, and when to leave a field empty.
This sample submission shows the required columns and cell format. Treat it as a format example, not as an additional source of product facts.
This companion file explains the input and output columns.*
This companion file describes the expected submission columns and the structure of JSON values inside CSV cells.
This archive contains downloadable product images for some records in the input files.
Use this file to match each record_id to its image filename in product_images.zip. A record with multiple images appears on multiple rows. An empty img_filename means no image for that record is included in the archive.