Triple

T16869327
Position Surface form Disambiguated ID Type / Status
Subject Central Indo-Aryan languages E410127 entity
Predicate majorLanguage P207 FINISHED
Object Bagheli E116304 NE FINISHED

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: [Central Indo-Aryan languages, majorLanguage, Bagheli]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bagheli
Context triple: [Central Indo-Aryan languages, majorLanguage, 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 (3 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_69d88395e6c88190b22730f335107c14 completed April 10, 2026, 4:59 a.m.
NER Named-entity recognition batch_69e3b50b85c08190b35d1c45ee0e9675 completed April 18, 2026, 4:44 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00c7a27f548190963c35f40f4420f8 completed May 10, 2026, 6 p.m.
Created at: April 10, 2026, 5:24 a.m.