Triple

T7856508
Position Surface form Disambiguated ID Type / Status
Subject Rawalpindi Railway Station E182388 entity
Predicate connectsTo P845 FINISHED
Object Attock E186757 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: Attock | Statement: [Rawalpindi Railway Station, connectsTo, Attock]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Attock
Context triple: [Rawalpindi Railway Station, connectsTo, Attock]
  • A. Attock chosen
    Attock is a historic city in northern Pakistan strategically located along the Indus River, long serving as a key gateway between the Punjab region and Khyber Pakhtunkhwa.
  • B. Haripur
    Haripur is a city in northern Pakistan known as an administrative and commercial center in the Hazara region of Khyber Pakhtunkhwa.
  • C. Panjgur
    Panjgur is a town and district headquarters in Pakistan’s Balochistan province, known for its date cultivation and location along historic trade routes.
  • D. Chakwal
    Chakwal is a city in Pakistan’s Punjab province, known as a regional administrative and commercial center in the Potohar Plateau area.
  • E. 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.
  • 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_69ca82887fd48190975896bf38c4596b completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb1a75de548190af5653409a3b3881 completed March 31, 2026, 12:51 a.m.
NED1 Entity disambiguation (via context triple) batch_69cde6a2bdd08190897705615109dae0 completed April 2, 2026, 3:46 a.m.
Created at: March 30, 2026, 4:52 p.m.