Triple

T613778
Position Surface form Disambiguated ID Type / Status
Subject Indus River E12157 entity
Predicate majorCityOnRiver P316 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: [Indus River, majorCityOnRiver, Sukkur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sukkur
Context triple: [Indus River, majorCityOnRiver, 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. Haripur
    Haripur is a city in northern Pakistan known as an administrative and commercial center in the Hazara region of Khyber Pakhtunkhwa.
  • C. Rawalpindi
    Rawalpindi is a major city in Pakistan’s Punjab province, historically significant as a former temporary national capital and now a key commercial and military center.
  • D. Lahore
    Lahore is a major cultural, historical, and economic center of Pakistan, known for its rich Mughal heritage, educational institutions, and role in the region’s political history.
  • E. Nawabshah
    Nawabshah is a major city in Pakistan known as an important commercial and agricultural center in the Sindh province.
  • 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_69a493309df48190a327f748e88049a6 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a49e08dbf88190ab050078a63e266b completed March 1, 2026, 8:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69a577891a148190ae1364191f7f63bb completed March 2, 2026, 11:42 a.m.
Created at: March 1, 2026, 7:35 p.m.