Triple

T7892413
Position Surface form Disambiguated ID Type / Status
Subject Swat District E183266 entity
Predicate hasArchaeologicalSite P1098 FINISHED
Object Barikot E272879 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: Barikot | Statement: [Swat District, hasArchaeologicalSite, Barikot]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Barikot
Context triple: [Swat District, hasArchaeologicalSite, Barikot]
  • A. Barikot chosen
    Barikot is an ancient archaeological and historical town in Pakistan’s Swat Valley, known for its strategic location and remains from Indo-Greek and Buddhist periods.
  • B. Barkot
    Barkot is a small town in Uttarkashi district of Uttarakhand, India, that serves as an important stopover and base for pilgrims traveling to the Yamunotri temple in the Garhwal Himalayas.
  • C. Barisakho
    Barisakho is a small mountain village in the historic Khevsureti region of northeastern Georgia, serving as one of its local centers.
  • D. Bara
    Bara is a town in Pakistan’s Khyber District, known as a key settlement in the Khyber Pass region with strategic and commercial significance.
  • E. Bonda
    Bonda is an archaeological site associated with the pre-Columbian Tairona culture in northern Colombia.
  • 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_69ca828c474c8190a254d6499871eaff completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb39fef2e48190a6282c217c33c57a completed March 31, 2026, 3:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69cb5ba51ee48190b654a931da2c049f completed March 31, 2026, 5:29 a.m.
Created at: March 30, 2026, 5 p.m.