Triple

T10576848
Position Surface form Disambiguated ID Type / Status
Subject Pavapuri E249630 entity
Predicate languageSpoken P151 FINISHED
Object Bhojpuri E32399 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: Bhojpuri | Statement: [Pavapuri, languageSpoken, Bhojpuri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bhojpuri
Context triple: [Pavapuri, languageSpoken, Bhojpuri]
  • A. Bhojpuri chosen
    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.
  • B. Bagheli
    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.
  • C. Maithili
    Maithili is an Indo-Aryan language spoken primarily in the eastern Indian state of Bihar and neighboring regions, with a rich literary tradition and official recognition in India.
  • D. Nagpuri
    Nagpuri is an Indo-Aryan language spoken primarily in parts of eastern India, especially in and around the present-day state of Jharkhand.
  • E. Santhali
    Santhali is an Austroasiatic language spoken primarily by the Santal people in eastern India, Bangladesh, Nepal, and Bhutan.
  • 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_69d381c8bd708190acf3d275c908251e completed April 6, 2026, 9:50 a.m.
NER Named-entity recognition batch_69d5275628988190bd00dd3f8d7c3937 completed April 7, 2026, 3:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69d94b65313481909328bd9f7f39bf53 completed April 10, 2026, 7:11 p.m.
Created at: April 6, 2026, 12:38 p.m.