Triple

T29041771
Position Surface form Disambiguated ID Type / Status
Subject Gujrat District E738013 entity
Predicate hasNotableTown P14082 FINISHED
Object Kotla Arab Ali Khan
Kotla Arab Ali Khan is a town in Pakistan’s Punjab province known for its location near the border with Azad Kashmir and its role as a local commercial and administrative center.
E1847464 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: Kotla Arab Ali Khan | Statement: [Gujrat District, hasNotableTown, Kotla Arab Ali Khan]
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: Kotla Arab Ali Khan
Triple: [Gujrat District, hasNotableTown, Kotla Arab Ali Khan]
Generated description
Kotla Arab Ali Khan is a town in Pakistan’s Punjab province known for its location near the border with Azad Kashmir and its role as a local commercial and administrative center.

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_69f077efb3848190b41574e1670f6ae2 completed April 28, 2026, 9:03 a.m.
NER Named-entity recognition batch_69f66041993c8190877d0d08d57dbac5 completed May 2, 2026, 8:36 p.m.
NED1 Entity disambiguation (via context triple) batch_6a251f6f12e48190bd034636e0434f8f completed June 7, 2026, 7:36 a.m.
NEDg Description generation batch_6a25236efee48190a290cafff34d247e completed June 7, 2026, 7:53 a.m.
NED2 Entity disambiguation (via description) batch_6a25272d01e88190a5a19b0d13415d36 completed June 7, 2026, 8:09 a.m.
Created at: April 28, 2026, 10:02 a.m.