Triple

T18199299
Position Surface form Disambiguated ID Type / Status
Subject Chenab Nagar E435739 entity
Predicate hasNearbyCity P350 FINISHED
Object Jhang 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: Jhang | Statement: [Chenab Nagar, hasNearbyCity, Jhang]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jhang
Context triple: [Chenab Nagar, hasNearbyCity, Jhang]
  • A. Jhang chosen
    Jhang is a historic city in the Punjab province of Pakistan, known for its cultural heritage and as the birthplace of several notable figures.
  • B. Gujranwala
    Gujranwala is a major industrial city in Pakistan’s Punjab province, known for its manufacturing base and historical significance in the region.
  • C. Chakwal
    Chakwal is a city in Pakistan’s Punjab province, known as a regional administrative and commercial center in the Potohar Plateau area.
  • D. Khanewal
    Khanewal is a prominent city in Pakistan’s Punjab province, known as an important railway junction and agricultural trade center.
  • E. Haripur
    Haripur is a city in northern Pakistan known as an administrative and commercial center in the Hazara region of Khyber Pakhtunkhwa.
  • 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_69d8b90dba6481908e119eb9aa4ca0cb completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4e0d545f4819090285d1446bd3c27 completed April 19, 2026, 2:04 p.m.
Created at: April 10, 2026, 10:31 a.m.