Triple

T23194174
Position Surface form Disambiguated ID Type / Status
Subject Gah E579828 entity
Predicate hasNearbyCity P350 FINISHED
Object Chakwal 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: Chakwal | Statement: [Gah, hasNearbyCity, Chakwal]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chakwal
Context triple: [Gah, hasNearbyCity, Chakwal]
  • A. Chakwal chosen
    Chakwal is a city in Pakistan’s Punjab province, known as a regional administrative and commercial center in the Potohar Plateau area.
  • B. Khanewal
    Khanewal is a prominent city in Pakistan’s Punjab province, known as an important railway junction and agricultural trade center.
  • C. Bahawalnagar
    Bahawalnagar is a prominent city in Pakistan’s Punjab province, known as an agricultural and commercial hub near the border with India.
  • D. Chakwal Potohari
    Chakwal Potohari is a regional dialect of the Potohari language spoken primarily in and around the Chakwal district of Pakistan’s Punjab province.
  • E. Sargodha
    Sargodha is a major city in central Pakistan known for its air force base and extensive citrus (particularly kinnow) production.
  • 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_69e24600eed08190bd7e5295653a1503 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18fda64cc8190aeb5ccd8d8d20858 completed April 29, 2026, 4:58 a.m.
Created at: April 17, 2026, 4:06 p.m.