Triple

T2440373
Position Surface form Disambiguated ID Type / Status
Subject Khyber Pass E53258 entity
Predicate locatedNear P294 FINISHED
Object Jalalabad E118245 NE FINISHED

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: Jalalabad | Statement: [Khyber Pass, locatedNear, Jalalabad]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jalalabad
Context triple: [Khyber Pass, locatedNear, Jalalabad]
  • A. Jalalabad, Afghanistan chosen
    Jalalabad, Afghanistan is a major city in eastern Afghanistan near the Khyber Pass, known as a historic cultural and trade center of the region.
  • B. Kandahar
    Kandahar is a historic city in southern Afghanistan that has long served as a major political, cultural, and commercial center in the region.
  • C. Quetta
    Quetta is a major city in western Pakistan known as the provincial capital of Balochistan and a key commercial and military center near the Afghan border.
  • D. Wazirabad
    Wazirabad is a city in the Gujranwala District of Punjab, Pakistan, known for its cutlery industry and strategic location near the Chenab River.
  • E. Peshawar
    Peshawar is one of Pakistan’s oldest and largest cities, a historic cultural and economic hub located near the Khyber Pass in the country’s northwest.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69ab495b6dac8190ac82661aa1452222 completed March 6, 2026, 9:38 p.m.
NER Named-entity recognition batch_69abc9f7ba208190810f8ea115110375 completed March 7, 2026, 6:47 a.m.
NED1 Entity disambiguation (via context triple) batch_69af178a0f0c81909f6629f3fed76e2c completed March 9, 2026, 6:55 p.m.
Created at: March 6, 2026, 9:43 p.m.