Triple

T19409796
Position Surface form Disambiguated ID Type / Status
Subject Gond people E485557 entity
Predicate relatedEthnicGroup P1969 FINISHED
Object Muria Gond 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: Muria Gond | Statement: [Gond people, relatedEthnicGroup, Muria Gond]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Muria Gond
Context triple: [Gond people, relatedEthnicGroup, Muria Gond]
  • A. Muria Gond chosen
    Muria Gond are an indigenous Adivasi community of central India, primarily known for their distinct social customs, youth dormitory traditions, and rich folk art and music within the broader Gond cultural group.
  • B. Mohanchoti
    Mohanchoti is an island located within Lake Pichola in Udaipur, Rajasthan, India.
  • C. Satpuli
    Satpuli is a small town in the Pauri Garhwal region of Uttarakhand, India, known as a local market and transit hub along the banks of the Nayar River in the Himalayan foothills.
  • D. Ormui
    Ormui is an alternative name for Ormur, a small Indo-Iranian ethnic group primarily residing in parts of Afghanistan and Pakistan.
  • E. Koya Gondi
    Koya Gondi is a dialect of the Gondi language spoken primarily by the Koya tribal communities in central India.
  • 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_69d8e8d5162481909db12435d9535c1a completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e62af3eaa081909e9537a2c57dc6c1 completed April 20, 2026, 1:32 p.m.
Created at: April 10, 2026, 1:37 p.m.