Triple

T21643968
Position Surface form Disambiguated ID Type / Status
Subject Banihal Pass E534167 entity
Predicate near P350 FINISHED
Object Banihal town 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: Banihal town | Statement: [Banihal Pass, near, Banihal town]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Banihal town
Context triple: [Banihal Pass, near, Banihal town]
  • A. Banihal chosen
    Banihal is a mountain town in the Jammu and Kashmir region of India, known for the Banihal Pass and its strategic location on the Jammu–Srinagar highway.
  • B. Kharsawan
    Kharsawan is a town in the Kolhan region of Jharkhand, India, known historically as a former princely state and a local administrative and commercial center.
  • C. Khajauli
    Khajauli is a town located in the Madhubani district of the Indian state of Bihar.
  • D. Hispar village
    Hispar village is a remote settlement in the Karakoram region of northern Pakistan, known as a gateway for trekkers and climbers heading to the Hispar Glacier and surrounding high mountains.
  • E. Naharkatiya town
    Naharkatiya town is a settlement in Assam, India, known for its proximity to one of the region’s earliest and most significant oil-producing areas.
  • 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_69e0c466aec88190ba39c7543dbc8ba2 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef53930644819086b0f499e1b8ae63 completed April 27, 2026, 12:16 p.m.
Created at: April 16, 2026, 6:35 p.m.