Triple

T21556136
Position Surface form Disambiguated ID Type / Status
Subject Banjara E531896 entity
Predicate language P15 FINISHED
Object Lambadi NE NERFINISHED

How this triple was built (2 steps)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Lambadi | Statement: [Banjara, language, Lambadi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lambadi
Context triple: [Banjara, language, Lambadi]
  • A. Lambadi chosen
    Lambadi is an Indo-Aryan language variety spoken primarily by the Lambadi (Banjara) community across parts of northwestern and central India.
  • B. Lambadi people
    The Lambadi people are a traditionally nomadic tribal community of India, known for their vibrant embroidered clothing, folk dances, and distinct language and customs.
  • C. Chenchu
    Chenchu is a Dravidian language spoken by the indigenous Chenchu people, primarily inhabiting forested regions of Andhra Pradesh and Telangana in India.
  • D. Dagara
    Dagara is a Gur language spoken primarily in parts of Ghana and Burkina Faso by the Dagara people.
  • E. Rabha
    Rabha are an indigenous ethnic group of Northeast India, primarily inhabiting Assam and Meghalaya, known for their distinct Tibeto-Burman language, agrarian lifestyle, and rich folk traditions.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 batches)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69e0c460232c81908de2c3819d17c00e completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69eed2df48c88190894b6b08a5cb6390 completed April 27, 2026, 3:07 a.m.
Created at: April 16, 2026, 6:29 p.m.