Triple

T17462059
Position Surface form Disambiguated ID Type / Status
Subject Yasin E425176 entity
Predicate near P350 FINISHED
Object Shandur Pass 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: Shandur Pass | Statement: [Yasin, near, Shandur Pass]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shandur Pass
Context triple: [Yasin, near, Shandur Pass]
  • A. Shandur Pass chosen
    Shandur Pass is a high-altitude mountain pass in northern Pakistan famed for its annual polo festival held on one of the world’s highest polo grounds.
  • B. Banihal Pass
    Banihal Pass is a high mountain pass in the Himalayas that serves as a key route connecting the Kashmir Valley with the rest of India.
  • C. Lowari Pass
    Lowari Pass is a high mountain pass in northern Pakistan that connects the Chitral region with the rest of Khyber Pakhtunkhwa through the Hindu Kush range.
  • D. Darkot Pass
    Darkot Pass is a high-altitude mountain pass in northern Pakistan that connects the Ghizer District of Gilgit-Baltistan with the Yasin and Chitral regions across the Hindu Kush range.
  • E. Hispar Pass
    Hispar Pass is a high-altitude mountain pass in the Karakoram range of Pakistan that forms a key glacial route linking the Hispar and Biafo Glaciers.
  • 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_69d889dbc2e88190b18ea6115e819258 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e451a3c4cc8190937808e3272272c0 completed April 19, 2026, 3:53 a.m.
Created at: April 10, 2026, 5:47 a.m.