Triple

T36830055
Position Surface form Disambiguated ID Type / Status
Subject Supaul Lok Sabha constituency E910113 entity
Predicate MPIn2009 P14470 FINISHED
Object Vishwamohan Kumar
Vishwamohan Kumar is an Indian politician who served as a Member of Parliament representing the Supaul Lok Sabha constituency in Bihar.
E2224906 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: Vishwamohan Kumar | Statement: [Supaul Lok Sabha constituency, MPIn2009, Vishwamohan Kumar]
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: Vishwamohan Kumar
Triple: [Supaul Lok Sabha constituency, MPIn2009, Vishwamohan Kumar]
Generated description
Vishwamohan Kumar is an Indian politician who served as a Member of Parliament representing the Supaul Lok Sabha constituency in Bihar.

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_69f76e7e9d60819092442fba73290a46 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f7cabcdebc81908ceab2adf9939551 completed May 3, 2026, 10:22 p.m.
NED1 Entity disambiguation (via context triple) batch_6a4076db9f108190b65dabe792e73af1 completed June 28, 2026, 1:20 a.m.
NEDg Description generation batch_6a4077aa5868819088b136de69926f01 completed June 28, 2026, 1:23 a.m.
NED2 Entity disambiguation (via description) batch_6a4078362d0881909b963ee3fe45787e completed June 28, 2026, 1:26 a.m.
Created at: May 3, 2026, 4:13 p.m.