Triple
T34505450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parihar Assembly constituency |
E885872
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Assembly constituency in Bihar |
C44644
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Assembly constituency in Bihar Context triple: [Parihar Assembly constituency, instanceOf, Assembly constituency in Bihar]
-
A.
Legislative Assembly constituency in India
chosen
A Legislative Assembly constituency in India is a geographically defined electoral district that elects one representative to the state’s Legislative Assembly.
-
B.
former Lok Sabha constituency
A former Lok Sabha constituency is an electoral district that once elected a representative to India’s lower house of Parliament but has since been dissolved, merged, or restructured through delimitation or administrative changes.
-
C.
Uttar Pradesh Legislative Assembly constituency
An Uttar Pradesh Legislative Assembly constituency is a defined electoral district within the Indian state of Uttar Pradesh from which voters elect one representative (MLA) to the Uttar Pradesh Legislative Assembly.
-
D.
Lok Sabha parliamentary constituency
A Lok Sabha parliamentary constituency is a geographically defined electoral district in India that elects one member to the lower house of Parliament, the Lok Sabha.
-
E.
Maharashtra legislative assembly constituency
A Maharashtra legislative assembly constituency is a defined territorial unit within the Indian state of Maharashtra that elects one representative (MLA) to the Maharashtra Vidhan Sabha.
- F. None of above.
Provenance (1 batch)
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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:01 a.m.