Triple

T25826088
Position Surface form Disambiguated ID Type / Status
Subject Bhopal Lok Sabha constituency E650532 entity
Predicate assemblySegment P63908 FINISHED
Object Bhopal Madhya
Bhopal Madhya is a legislative assembly constituency located in the central part of Bhopal city in the Indian state of Madhya Pradesh.
E1719543 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: Bhopal Madhya | Statement: [Bhopal Lok Sabha constituency, assemblySegment, Bhopal Madhya]
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: Bhopal Madhya
Triple: [Bhopal Lok Sabha constituency, assemblySegment, Bhopal Madhya]
Generated description
Bhopal Madhya is a legislative assembly constituency located in the central part of Bhopal city in the Indian state of Madhya Pradesh.

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_6a118f85aabc8190884c50b120dd878d completed May 23, 2026, 11:29 a.m.
NEDg Description generation batch_6a119053e3b0819092c8e62b5b4ae02a completed May 23, 2026, 11:32 a.m.
NED2 Entity disambiguation (via description) batch_6a1190db5ab48190a5b902fee03abdde completed May 23, 2026, 11:34 a.m.
Created at: April 22, 2026, 7:36 a.m.