Triple

T38175791
Position Surface form Disambiguated ID Type / Status
Subject Balachaur tehsil E1000207 entity
Predicate partOf P40 FINISHED
Object Balachaur subdivision
Balachaur subdivision is an administrative subdivision in Punjab, India, overseeing local governance and development for the Balachaur area and surrounding regions.
E2260112 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: Balachaur subdivision | Statement: [Balachaur tehsil, partOf, Balachaur subdivision]
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: Balachaur subdivision
Triple: [Balachaur tehsil, partOf, Balachaur subdivision]
Generated description
Balachaur subdivision is an administrative subdivision in Punjab, India, overseeing local governance and development for the Balachaur area and surrounding regions.

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_69f76daaace48190a38cee37f8ce343f completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69fcb0ff67088190b7fa6d05b5d8043e completed May 7, 2026, 3:34 p.m.
NED1 Entity disambiguation (via context triple) batch_6a417b33c4b4819085b225889292d2f7 completed June 28, 2026, 7:51 p.m.
NEDg Description generation batch_6a417baa1b5c81908348dd8216755417 completed June 28, 2026, 7:53 p.m.
NED2 Entity disambiguation (via description) batch_6a417fb32bbc81908dbaec32269b2b89 completed June 28, 2026, 8:10 p.m.
Created at: May 3, 2026, 4:29 p.m.