Triple

T22042791
Position Surface form Disambiguated ID Type / Status
Subject Sarazi E544680 entity
Predicate subfamily P4180 FINISHED
Object Western Pahari 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: Western Pahari | Statement: [Sarazi, subfamily, Western Pahari]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Western Pahari
Context triple: [Sarazi, subfamily, Western Pahari]
  • A. Western Pahari chosen
    Western Pahari is a group of closely related Indo-Aryan languages spoken primarily in the hilly regions of Himachal Pradesh and surrounding areas in northern India.
  • B. Central Pahari
    Central Pahari is a subgroup of Indo-Aryan languages spoken in the central Himalayan region of India, particularly in parts of Uttarakhand and neighboring areas.
  • C. Eastern Pahari
    Eastern Pahari is a group of Indo-Aryan languages spoken primarily in the eastern Himalayan region, including varieties such as Nepali.
  • D. Pahari
    Pahari is an Indo-Aryan language spoken by communities in the Jammu region of northern India, closely related to other Western Pahari dialects of the Himalayas.
  • E. Pahari
    Pahari is a town located in India’s culturally significant Braj region, known for its association with Hindu religious traditions and heritage.
  • 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_69e11e32445c8190ab97089b48a130bb completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f1282ac42c819099b2f664f79f5b83 completed April 28, 2026, 9:35 p.m.
Created at: April 16, 2026, 8:25 p.m.