Triple

T15626948
Position Surface form Disambiguated ID Type / Status
Subject Balti language E375700 entity
Predicate hasAlternativeName P39 FINISHED
Object Balti Bhoti E1168794 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: Balti Bhoti | Statement: [Balti language, hasAlternativeName, Balti Bhoti]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Balti Bhoti
Context triple: [Balti language, hasAlternativeName, Balti Bhoti]
  • A. བལྟི (Balti) chosen
    བལྟི (Balti) refers to the Balti people, an ethnic group of Tibetan origin primarily inhabiting the Baltistan region in the northern areas of Pakistan and parts of India.
  • B. Bhutia
    Bhutia is a Sino-Tibetan language spoken primarily by the Bhutia community in the Himalayan regions of India, especially in Sikkim and parts of West Bengal.
  • C. Garhwali
    Garhwali is an Indo-Aryan language spoken primarily in the Garhwal region of the Indian state of Uttarakhand.
  • D. Dholuo
    Dholuo is a Nilotic language spoken primarily by the Luo people of western Kenya and parts of Tanzania.
  • E. Rajbanshi language
    Rajbanshi language is an Eastern Indo-Aryan language spoken primarily in parts of India, Nepal, and Bangladesh by the Rajbanshi ethnic 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_69d85cd035a48190b73d5579ab73969a completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04e9e5e248190ae54cda1fde51efb completed April 16, 2026, 2:51 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff678c9d8c8190be73b6e7ed558e99 completed May 9, 2026, 4:57 p.m.
Created at: April 10, 2026, 4:14 a.m.