Triple

T4871608
Position Surface form Disambiguated ID Type / Status
Subject Jharkhand Mukti Morcha E109095 entity
Predicate languageOfPolitics P11589 FINISHED
Object Nagpuri E301323 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: Nagpuri | Statement: [Jharkhand Mukti Morcha, languageOfPolitics, Nagpuri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nagpuri
Context triple: [Jharkhand Mukti Morcha, languageOfPolitics, Nagpuri]
  • A. Nagpuri chosen
    Nagpuri is an Indo-Aryan language spoken primarily in parts of eastern India, especially in and around the present-day state of Jharkhand.
  • B. Kurukh
    Kurukh is an indigenous Dravidian language spoken primarily by the Oraon tribal communities in eastern and central India.
  • C. 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.
  • 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. 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.
  • 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_69bd440d96a48190b0c87069adef2af1 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6d9c77b88190b3e6884c9752ebbb completed March 20, 2026, 3:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69be7793405c81909af7de2ad8e62e54 completed March 21, 2026, 10:48 a.m.
Created at: March 20, 2026, 1:27 p.m.