Triple

T10171389
Position Surface form Disambiguated ID Type / Status
Subject Vasi people E235337 entity
Predicate nativeLanguage P151 FINISHED
Object Prasun language E45675 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: Prasun language | Statement: [Vasi people, nativeLanguage, Prasun language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Prasun language
Context triple: [Vasi people, nativeLanguage, Prasun language]
  • A. Prasun language chosen
    The Prasun language is a Nuristani language spoken by the Prasun (Vasi) people in parts of eastern Afghanistan.
  • B. Prinmi language
    The Prinmi language is a Sino-Tibetan language spoken primarily by the Pumi people of southwestern China, noted for its complex phonology and role in the Qiangic branch.
  • C. Belhare language
    The Belhare language is a Kiranti language of the Sino-Tibetan family spoken by the Belhare community in eastern Nepal.
  • D. Padam language
    Padam language is a Tani (Sino-Tibetan) language of northeastern India spoken by the Padam subgroup of the Mishing/Adi peoples of Arunachal Pradesh and Assam.
  • E. Tipra language
    Tipra language, also known as Kokborok, is a Tibeto-Burman language spoken primarily by the Tripuri people of the Indian state of Tripura and surrounding regions.
  • 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_69ca84ceafd0819085828600e11bed6b completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdec9e4e0c819097dceb7bf7757948 completed April 2, 2026, 4:12 a.m.
NED1 Entity disambiguation (via context triple) batch_69d3178844c48190af952ac30a4d6d97 completed April 6, 2026, 2:16 a.m.
Created at: March 30, 2026, 9:10 p.m.