Triple

T22048310
Position Surface form Disambiguated ID Type / Status
Subject Banjara people E544818 entity
Predicate alsoKnownAs P39 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 people, alsoKnownAs, Lambadi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lambadi
Context triple: [Banjara people, alsoKnownAs, 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_69e11e32445c8190ab97089b48a130bb completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f1283191e48190b4ddc84138243327 completed April 28, 2026, 9:35 p.m.
Created at: April 16, 2026, 8:26 p.m.