Triple

T17397535
Position Surface form Disambiguated ID Type / Status
Subject Bikhauti E422991 entity
Predicate languageContext P36 FINISHED
Object Garhwali NE NERFINISHED

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: [Bikhauti, languageContext, Garhwali]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Garhwali
Context triple: [Bikhauti, languageContext, Garhwali]
  • A. Garhwali chosen
    Garhwali is an Indo-Aryan language spoken primarily in the Garhwal region of the Indian state of Uttarakhand.
  • B. Garhwali people
    The Garhwali people are an Indo-Aryan ethnic group native to the Garhwal region of Uttarakhand in the Indian Himalayas, known for their distinct language, folk traditions, and mountain agrarian culture.
  • C. Gojri
    Gojri is an Indo-Aryan language traditionally spoken by the Gujjar community across parts of northern India and Pakistan.
  • D. 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.
  • E. 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.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d889d710288190bf0f4762801fefae completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e43abe6f708190944aad636e1eb9a1 completed April 19, 2026, 2:15 a.m.
Created at: April 10, 2026, 5:45 a.m.