Triple

T5113449
Position Surface form Disambiguated ID Type / Status
Subject Bolpur subdivision E115270 entity
Predicate languageSpoken P151 FINISHED
Object Santali E38852 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: Santali | Statement: [Bolpur subdivision, languageSpoken, Santali]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Santali
Context triple: [Bolpur subdivision, languageSpoken, Santali]
  • A. Santhali chosen
    Santhali is an Austroasiatic language spoken primarily by the Santal people in eastern India, Bangladesh, Nepal, and Bhutan.
  • 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. Kurukh
    Kurukh is an indigenous Dravidian language spoken primarily by the Oraon tribal communities in eastern and central India.
  • D. 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.
  • E. Mundari
    Mundari is an Austroasiatic Munda language of eastern India, spoken primarily by the Munda people in states such as Jharkhand, Odisha, and West Bengal.
  • 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_69bd4441d1648190a54a533895041987 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd75cba1e88190af076657f846b975 completed March 20, 2026, 4:28 p.m.
NED1 Entity disambiguation (via context triple) batch_69bebaaa394c8190bd93cdf57475a5b6 completed March 21, 2026, 3:35 p.m.
Created at: March 20, 2026, 1:41 p.m.