Triple
T30794902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koppal Assembly constituency |
E784201
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | State legislative assembly constituency in India |
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: State legislative assembly constituency in India Context triple: [Koppal Assembly constituency, instanceOf, State legislative assembly constituency in India]
-
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.
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.
-
C.
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.
-
D.
Tamil Nadu State Legislative Assembly constituency
A Tamil Nadu State Legislative Assembly constituency is a geographically defined electoral division within the Indian state of Tamil Nadu that elects one representative (MLA) to the Tamil Nadu Legislative Assembly.
-
E.
Rajasthan Legislative Assembly constituency
A Rajasthan Legislative Assembly constituency is a defined electoral district within the Indian state of Rajasthan from which voters elect one representative to the Rajasthan Legislative Assembly.
- 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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:42 p.m.