Triple

T21201087
Position Surface form Disambiguated ID Type / Status
Subject New Indo-Aryan languages E522454 entity
Predicate hasPart P35 FINISHED
Object Bagheli 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: Bagheli | Statement: [New Indo-Aryan languages, hasPart, Bagheli]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bagheli
Context triple: [New Indo-Aryan languages, hasPart, Bagheli]
  • A. Bagheli chosen
    Bagheli is an Indo-Aryan language spoken primarily in the Bagelkhand region of central India, closely related to Hindi and used by millions as a regional vernacular.
  • B. Nagpuri
    Nagpuri is an Indo-Aryan language spoken primarily in parts of eastern India, especially in and around the present-day state of Jharkhand.
  • C. Bhojpuri
    Bhojpuri is an Indo-Aryan language spoken primarily in eastern Uttar Pradesh, western Bihar, and parts of Nepal, with a rich folk culture and a large diaspora community.
  • D. Mirpuri
    Mirpuri is a major dialect of the Lahnda (Western Punjabi) language, primarily spoken in the Mirpur region of Azad Kashmir and among its diaspora communities.
  • E. Mayurkhandi
    Mayurkhandi is an early historic town in India that once served as a former capital of the Rashtrakuta dynasty.
  • 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_69e0b5112d8881909510b2dcdc93106d completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e73430c5a08190aeb6a62eec0f43a3 completed April 21, 2026, 8:24 a.m.
Created at: April 16, 2026, 3:18 p.m.