Triple

T13885810
Position Surface form Disambiguated ID Type / Status
Subject Western Pahari E333839 entity
Predicate hasDialect P4251 FINISHED
Object Churahi E1068664 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: Churahi | Statement: [Western Pahari, hasDialect, Churahi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Churahi
Context triple: [Western Pahari, hasDialect, Churahi]
  • A. Churahi chosen
    Churahi is an Indo-Aryan language variety spoken in the Chamba region of Himachal Pradesh, India, and is considered part of the Western Pahari group.
  • B. Chakia
    Chakia is a town in the East Champaran district of the Indian state of Bihar, known primarily as a local administrative and market center for the surrounding rural region.
  • C. Chitrali
    Chitrali is an alternative name for Khowar, an Indo-Aryan language spoken primarily in Pakistan’s Chitral region.
  • D. Chakosi
    Chakosi is a Gur language spoken primarily by the Chakosi (Anufo) people in parts of Ghana, Togo, and Benin.
  • E. Chaam
    Chaam is a village in the Dutch province of North Brabant, known for its rural character and historic ties to the Baronie of Breda.
  • 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_69d81c5dd2d48190b7a5fc1e009de936 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de23a101488190bd790b28033d38b9 completed April 14, 2026, 11:23 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7ce6facd48190b310099fbd52bdf0 completed May 3, 2026, 10:38 p.m.
Created at: April 9, 2026, 10:15 p.m.