Triple

T21968875
Position Surface form Disambiguated ID Type / Status
Subject Pahari people E542529 entity
Predicate hasEthnicIdentity P27835 FINISHED
Object 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: Pahari | Statement: [Pahari people, hasEthnicIdentity, Pahari]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pahari
Context triple: [Pahari people, hasEthnicIdentity, Pahari]
  • A. Pahari
    Pahari is a town located in India’s culturally significant Braj region, known for its association with Hindu religious traditions and heritage.
  • B. Pahari chosen
    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.
  • C. Chamba Pahari
    Chamba Pahari is an Indo-Aryan language variety spoken in and around the Chamba region of Himachal Pradesh in northern India.
  • D. Pahari-Potohari
    Pahari-Potohari is an Indo-Aryan language variety spoken primarily in the Potohar Plateau and surrounding regions of northern Pakistan, often considered a transitional form between Punjabi and Hindko.
  • E. Kangra Pahari
    Kangra Pahari is an Indo-Aryan language variety spoken in the Kangra region of Himachal Pradesh in northern India.
  • 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_69e0c48070988190909db97667b9a0ac completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f1245d50d08190a4bf93139daa77eb completed April 28, 2026, 9:19 p.m.
Created at: April 16, 2026, 8:02 p.m.