Triple

T8420658
Position Surface form Disambiguated ID Type / Status
Subject Hindko E198840 entity
Predicate spokenInCity P8343 FINISHED
Object Mansehra E53257 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: Mansehra | Statement: [Hindko, spokenInCity, Mansehra]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mansehra
Context triple: [Hindko, spokenInCity, Mansehra]
  • A. Mansehra chosen
    Mansehra is a major city in northern Pakistan known as a gateway to the Kaghan Valley and the Karakoram Highway.
  • B. Baramulla
    Baramulla is a town in the Indian union territory of Jammu and Kashmir, known as a historic gateway to the Kashmir Valley and an important settlement along the Jhelum River.
  • C. Parachinar
    Parachinar is a major town in northwestern Pakistan near the Afghan border, known as the administrative center of Kurram District and for its strategic and sectarian-sensitive location.
  • D. Nowshera
    Nowshera is a city in northern Pakistan known as an important commercial and military center in the Khyber Pakhtunkhwa province.
  • E. Budgam
    Budgam is a town in the central part of the Kashmir region of India, serving as the administrative headquarters of Budgam district.
  • 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_69ca8312d63c8190bf133b676b44a385 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cb84ca7b348190abab25e79b05407f completed March 31, 2026, 8:24 a.m.
NED1 Entity disambiguation (via context triple) batch_69ce1d469a148190a6f018f758cba5eb completed April 2, 2026, 7:39 a.m.
Created at: March 30, 2026, 6:06 p.m.