Triple

T22313492
Position Surface form Disambiguated ID Type / Status
Subject Kishtwari E551582 entity
Predicate hasAlternativeName P39 FINISHED
Object Kishtwari Bhaderwahi 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: Kishtwari Bhaderwahi | Statement: [Kishtwari, hasAlternativeName, Kishtwari Bhaderwahi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kishtwari Bhaderwahi
Context triple: [Kishtwari, hasAlternativeName, Kishtwari Bhaderwahi]
  • A. Kishtwari chosen
    Kishtwari is an Indo-Aryan language spoken primarily in the Kishtwar region of Jammu and Kashmir, India.
  • B. Bawani Khera
    Bawani Khera is a town and state legislative assembly constituency in the Bhiwani district of Haryana, India.
  • C. Kharbanda
    Kharbanda is the birth name of Öljeitü, the Ilkhanid ruler of Persia in the early 14th century.
  • D. Rikhawdar
    Rikhawdar is a town in Myanmar located along the India–Myanmar border, serving as a key local hub for cross-border trade and movement.
  • E. Shakargarh
    Shakargarh is a town in Punjab, Pakistan, known for its agricultural surroundings and proximity to the border with 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_69e11e4776588190abb21e5cea79973f completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15750f76c81909d6f788928f503f1 completed April 29, 2026, 12:56 a.m.
Created at: April 16, 2026, 8:42 p.m.