Triple

T20146210
Position Surface form Disambiguated ID Type / Status
Subject Korku E491308 entity
Predicate closelyRelatedTo P37 FINISHED
Object Santali NE NERFINISHED

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: [Korku, closelyRelatedTo, Santali]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Santali
Context triple: [Korku, closelyRelatedTo, Santali]
  • A. Santhali chosen
    Santhali is an Austroasiatic language spoken primarily by the Santal people in eastern India, Bangladesh, Nepal, and Bhutan.
  • B. Bastar Gondi
    Bastar Gondi is a regional variety of the Gondi language spoken primarily by the Gond people in the Bastar region of central India.
  • C. Nagpuri
    Nagpuri is an Indo-Aryan language spoken primarily in parts of eastern India, especially in and around the present-day state of Jharkhand.
  • D. Kurukh
    Kurukh is an indigenous Dravidian language spoken primarily by the Oraon tribal communities in eastern and central India.
  • E. Birhor language
    Birhor language is an endangered Munda language of the Austroasiatic family spoken by the Birhor indigenous community in eastern India.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69da6265f8f0819080b29c752a574088 completed April 11, 2026, 3:01 p.m.
NER Named-entity recognition batch_69e6679e43a48190b3a5da5710b07ff7 completed April 20, 2026, 5:51 p.m.
Created at: April 11, 2026, 11:33 p.m.