Triple

T8559648
Position Surface form Disambiguated ID Type / Status
Subject Uttarkashi district E202657 entity
Predicate commonlySpokenLanguage P7445 FINISHED
Object Garhwali E169341 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: Garhwali | Statement: [Uttarkashi district, commonlySpokenLanguage, Garhwali]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Garhwali
Context triple: [Uttarkashi district, commonlySpokenLanguage, Garhwali]
  • A. Garhwali chosen
    Garhwali is an Indo-Aryan language spoken primarily in the Garhwal region of the Indian state of Uttarakhand.
  • B. Gojri
    Gojri is an Indo-Aryan language traditionally spoken by the Gujjar community across parts of northern India and Pakistan.
  • C. Dogri
    Dogri is an Indo-Aryan language spoken primarily in the Jammu region of India and surrounding areas, recognized as one of the official languages of India.
  • D. 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.
  • E. Pahari-Pothwari
    Pahari-Pothwari is an Indo-Aryan language variety spoken primarily in the Pothohar Plateau of northern Pakistan and adjoining regions, often considered transitional between Punjabi and Hindko.
  • 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_69ca8326e6c881908ff720d6abaebdc5 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe949974c8190a75d9c767ca5fa5a completed March 31, 2026, 3:33 p.m.
NED1 Entity disambiguation (via context triple) batch_69ce894d82588190b558d5b2dc65eafe completed April 2, 2026, 3:20 p.m.
Created at: March 30, 2026, 6:20 p.m.