Triple

T1945970
Position Surface form Disambiguated ID Type / Status
Subject Austroasiatic E42054 entity
Predicate majorLanguage P207 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: [Austroasiatic, majorLanguage, Santali]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Santali
Context triple: [Austroasiatic, majorLanguage, Santali]
  • A. Santhali chosen
    Santhali is an Austroasiatic language spoken primarily by the Santal people in eastern India, Bangladesh, Nepal, and Bhutan.
  • B. Kurukh
    Kurukh is an indigenous Dravidian language spoken primarily by the Oraon tribal communities in eastern and central India.
  • 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. 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.
  • E. 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.
  • 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_69a8870e08fc8190a319cbf2600db15f completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb300af2481908ae359972843c1ef completed March 7, 2026, 5:09 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae0ac7cd1881908d9284370de529ce completed March 8, 2026, 11:48 p.m.
Created at: March 4, 2026, 7:36 p.m.