Triple

T21917418
Position Surface form Disambiguated ID Type / Status
Subject Naipali E541215 entity
Predicate closelyRelatedTo P37 FINISHED
Object Garhwali language 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 language | Statement: [Naipali, closelyRelatedTo, Garhwali language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Garhwali language
Context triple: [Naipali, closelyRelatedTo, Garhwali language]
  • A. Garhwali chosen
    Garhwali is an Indo-Aryan language spoken primarily in the Garhwal region of the Indian state of Uttarakhand.
  • B. Gorkha language
    The Gorkha language, also known as Gorkhali, is an Indo-Aryan language historically associated with the Gorkha people of Nepal and closely related to standard Nepali.
  • C. Chamba language
    The Chamba language is a Niger-Congo language spoken by the Chamba people of Nigeria and Cameroon.
  • 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. Khaling language
    The Khaling language is a Kiranti Sino-Tibetan language spoken by the Khaling ethnic group in eastern Nepal, noted for its complex verbal morphology and rich consonant system.
  • 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_69e0c47c4b9c8190a5586a75f5f36453 completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f1233858308190a877d8015db4d380 completed April 28, 2026, 9:14 p.m.
Created at: April 16, 2026, 7:43 p.m.