Triple

T413261
Position Surface form Disambiguated ID Type / Status
Subject Khyber Pakhtunkhwa E9536 entity
Predicate hasCity P316 FINISHED
Object Peshawar E53256 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: Peshawar | Statement: [Khyber Pakhtunkhwa, hasCity, Peshawar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Peshawar
Context triple: [Khyber Pakhtunkhwa, hasCity, Peshawar]
  • A. Peshawar chosen
    Peshawar is one of Pakistan’s oldest and largest cities, a historic cultural and economic hub located near the Khyber Pass in the country’s northwest.
  • B. Quetta
    Quetta is a major city in western Pakistan known as the provincial capital of Balochistan and a key commercial and military center near the Afghan border.
  • C. Rawalpindi
    Rawalpindi is a major city in Pakistan’s Punjab province, historically significant as a former temporary national capital and now a key commercial and military center.
  • D. Haripur
    Haripur is a city in northern Pakistan known as an administrative and commercial center in the Hazara region of Khyber Pakhtunkhwa.
  • E. Islamabad
    Islamabad is Pakistan’s planned, modern capital city known for its high standard of living, greenery, and role as the country’s political and administrative center.
  • 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_69a2e80111fc8190961d5b7c6154123f completed Feb. 28, 2026, 1:05 p.m.
NER Named-entity recognition batch_69a2ecdc422881908910428fd1aee7c6 completed Feb. 28, 2026, 1:25 p.m.
NED1 Entity disambiguation (via context triple) batch_69a42f6278808190be4432cf305f525c completed March 1, 2026, 12:21 p.m.
Created at: Feb. 28, 2026, 1:09 p.m.