Triple

T6921824
Position Surface form Disambiguated ID Type / Status
Subject Khairpur E160202 entity
Predicate hasNearbyCity P350 FINISHED
Object Sukkur E77817 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: Sukkur | Statement: [Khairpur, hasNearbyCity, Sukkur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sukkur
Context triple: [Khairpur, hasNearbyCity, Sukkur]
  • A. Sukkur chosen
    Sukkur is a major city in Pakistan known for its strategic location on the Indus River and its role as an important commercial and cultural center in northern Sindh.
  • B. Faisalabad
    Faisalabad is a major industrial city in Pakistan’s Punjab province, known especially for its large textile industry and role as a commercial hub.
  • C. Multan
    Multan is a historic city in southern Punjab, Pakistan, renowned as a major cultural, commercial, and Sufi spiritual center with a legacy spanning over two millennia.
  • D. Bahawalnagar
    Bahawalnagar is a prominent city in Pakistan’s Punjab province, known as an agricultural and commercial hub near the border with India.
  • E. Rahim Yar Khan
    Rahim Yar Khan is a major city in southern Punjab, Pakistan, known as an important commercial and agricultural center in the Seraiki-speaking region.
  • 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_69c6884d350081908d8a970e4d40ad78 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6d9fb8ac48190b50bbc47fad8288f completed March 27, 2026, 7:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69c75137dd848190b35ff72725f886ba completed March 28, 2026, 3:55 a.m.
Created at: March 27, 2026, 2:26 p.m.