Triple

T5717027
Position Surface form Disambiguated ID Type / Status
Subject Khas Kura E126047 entity
Predicate subclassOf P1244 FINISHED
Object Pahari language E333837 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: Pahari language | Statement: [Khas Kura, subclassOf, Pahari language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pahari language
Context triple: [Khas Kura, subclassOf, Pahari language]
  • A. Western Pahari language chosen
    Western Pahari language is a group of Indo-Aryan languages spoken primarily in the hilly regions of Himachal Pradesh and surrounding areas in northern India.
  • B. Garhwali
    Garhwali is an Indo-Aryan language spoken primarily in the Garhwal region of the Indian state of Uttarakhand.
  • C. Mirpuri
    Mirpuri is a major dialect of the Lahnda (Western Punjabi) language, primarily spoken in the Mirpur region of Azad Kashmir and among its diaspora communities.
  • D. Kalasha language
    The Kalasha language is an endangered Indo-Aryan language spoken by the Kalash people in the remote valleys of Chitral District in northern Pakistan.
  • E. Bihari languages
    Bihari languages are a group of closely related Indo-Aryan languages spoken primarily in the Bihar region of eastern India and neighboring areas.
  • 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_69c0082e3d548190950169847b43043b completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c024ba819c8190bb7d775405dda9d6 completed March 22, 2026, 5:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69c05a7af5788190827ff8050eb6416d completed March 22, 2026, 9:09 p.m.
Created at: March 22, 2026, 3:46 p.m.