Triple

T12754221
Position Surface form Disambiguated ID Type / Status
Subject Narowal E304814 entity
Predicate hasNearbyCity P350 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: [Narowal, hasNearbyCity, Gujranwala]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gujranwala
Context triple: [Narowal, hasNearbyCity, 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_69d7bdf1fcd081909ffb0e0d6fa3a07d completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96d89ea70819098c470344f172167 completed April 10, 2026, 9:37 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6fefabc8081908e46ffcaef22cce1 completed May 3, 2026, 7:53 a.m.
Created at: April 9, 2026, 5:27 p.m.