Triple

T27480759
Position Surface form Disambiguated ID Type / Status
Subject Achin District E693592 entity
Predicate hasBorderingDistrict P224 FINISHED
Object Kot District
Kot District is an administrative district in eastern Afghanistan’s Nangarhar Province, known for its rural communities and proximity to the Pakistan border.
E1809882 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: Kot District | Statement: [Achin District, hasBorderingDistrict, Kot District]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Kot District
Triple: [Achin District, hasBorderingDistrict, Kot District]
Generated description
Kot District is an administrative district in eastern Afghanistan’s Nangarhar Province, known for its rural communities and proximity to the Pakistan border.

Provenance (5 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_69ef5381f2648190a2392d0fab833095 completed April 27, 2026, 12:16 p.m.
NER Named-entity recognition batch_69f62e47d5148190bff308cf49612191 completed May 2, 2026, 5:03 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1606eb2658819082d0580313f153aa completed May 26, 2026, 8:47 p.m.
NEDg Description generation batch_6a160be48fc48190a447fef91a58282c completed May 26, 2026, 9:08 p.m.
NED2 Entity disambiguation (via description) batch_6a160c61f0a88190800ca660556b612f completed May 26, 2026, 9:10 p.m.
Created at: April 27, 2026, 12:59 p.m.