Triple

T14555358
Position Surface form Disambiguated ID Type / Status
Subject Gujranwala Division E341522 entity
Predicate hasMajorCity P316 FINISHED
Object Gujranwala E68483 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: Gujranwala | Statement: [Gujranwala Division, hasMajorCity, Gujranwala]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gujranwala
Context triple: [Gujranwala Division, hasMajorCity, Gujranwala]
  • A. Gujranwala chosen
    Gujranwala is a major industrial city in Pakistan’s Punjab province, known for its manufacturing base and historical significance in the region.
  • B. Jhang
    Jhang is a historic city in the Punjab province of Pakistan, known for its cultural heritage and as the birthplace of several notable figures.
  • C. Khanewal
    Khanewal is a prominent city in Pakistan’s Punjab province, known as an important railway junction and agricultural trade center.
  • D. 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.
  • E. Vehari
    Vehari is a city in the Punjab province of Pakistan, known as an agricultural and educational hub in the 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_69d822db9c8481908213ceb39585f792 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb2f1490881908673f429e5288c86 completed April 14, 2026, 9:34 p.m.
NED1 Entity disambiguation (via context triple) batch_69fe3880ee4081908e783231de226448 completed May 8, 2026, 7:24 p.m.
Created at: April 10, 2026, 1:23 a.m.