Triple

T12058622
Position Surface form Disambiguated ID Type / Status
Subject Kohat Plateau E287106 entity
Predicate near P350 FINISHED
Object Kohat city E925606 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: Kohat city | Statement: [Kohat Plateau, near, Kohat city]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kohat city
Context triple: [Kohat Plateau, near, Kohat city]
  • A. Kohat city chosen
    Kohat city is an urban center in Pakistan’s Khyber Pakhtunkhwa province, known for its strategic location, military cantonment, and role as the administrative and commercial hub of Kohat District.
  • B. Kokota
    Kokota is an Oceanic language spoken in the Solomon Islands, particularly on Santa Isabel Island.
  • C. Koṭa
    Koṭa is a Dravidian language spoken by the indigenous Kota people in the Nilgiri Hills of southern India.
  • D. Saku City
    Saku City is a regional city in eastern Nagano Prefecture, Japan, known for its scenic highland landscapes, agriculture, and role as a local commercial and transportation hub.
  • E. Kota
    Kota is a major industrial and educational city in southeastern Rajasthan, India, known for its coaching institutes and power plants along the Chambal River.
  • 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_69d6ab4780948190bdb9f7620c2ac27e completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d9043dbccc8190bf9da181f826f0d8 completed April 10, 2026, 2:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69f49df216bc8190933e08f495f4d22f completed May 1, 2026, 12:34 p.m.
Created at: April 8, 2026, 9:47 p.m.