Triple

T25826098
Position Surface form Disambiguated ID Type / Status
Subject Bhopal Lok Sabha constituency E650532 entity
Predicate previouslyRepresentedBy P45113 FINISHED
Object Sushil Chandra Verma
Sushil Chandra Verma was an Indian politician who served as a Member of Parliament representing the Bhopal Lok Sabha constituency.
E1751643 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: Sushil Chandra Verma | Statement: [Bhopal Lok Sabha constituency, previouslyRepresentedBy, Sushil Chandra Verma]
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: Sushil Chandra Verma
Triple: [Bhopal Lok Sabha constituency, previouslyRepresentedBy, Sushil Chandra Verma]
Generated description
Sushil Chandra Verma was an Indian politician who served as a Member of Parliament representing the Bhopal Lok Sabha constituency.

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_69e7ab37438081908f1ccf6284839520 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f601954a68819083f749ed4b29a059 completed May 2, 2026, 1:52 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12296b269c819095b3684e0ac7735d completed May 23, 2026, 10:25 p.m.
NEDg Description generation batch_6a122d440b188190a9f30a83dde37fd8 completed May 23, 2026, 10:42 p.m.
NED2 Entity disambiguation (via description) batch_6a122d9d354481908564d175114e75eb completed May 23, 2026, 10:43 p.m.
Created at: April 22, 2026, 7:36 a.m.