Triple

T21478558
Position Surface form Disambiguated ID Type / Status
Subject Karachi–Peshawar Railway Line E529925 entity
Predicate connectsCity P4245 FINISHED
Object Bahawalpur 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: Bahawalpur | Statement: [Karachi–Peshawar Railway Line, connectsCity, Bahawalpur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bahawalpur
Context triple: [Karachi–Peshawar Railway Line, connectsCity, Bahawalpur]
  • A. Bahawalpur chosen
    Bahawalpur is a historic city in southern Punjab, Pakistan, known for its former princely state status, grand palaces, and proximity to the Cholistan Desert.
  • B. Bahawalnagar
    Bahawalnagar is a prominent city in Pakistan’s Punjab province, known as an agricultural and commercial hub near the border with India.
  • C. Khairpur
    Khairpur is a historic city in Sindh, Pakistan, known for its former princely state status under the Talpur rulers and its rich cultural and architectural heritage.
  • D. Khanewal
    Khanewal is a prominent city in Pakistan’s Punjab province, known as an important railway junction and agricultural trade center.
  • E. Chakwal
    Chakwal is a city in Pakistan’s Punjab province, known as a regional administrative and commercial center in the Potohar Plateau area.
  • 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_69e0c45acc3881908e38d3f28964152b completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69e9ea1951fc8190910f634327aa5c3f completed April 23, 2026, 9:44 a.m.
Created at: April 16, 2026, 6:20 p.m.