Triple
T26227500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mughalsarai Assembly constituency |
E655935
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Uttar Pradesh Assembly constituency |
C44470
|
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: Uttar Pradesh Assembly constituency Context triple: [Mughalsarai Assembly constituency, instanceOf, Uttar Pradesh Assembly constituency]
-
A.
Uttar Pradesh Legislative Assembly constituency
chosen
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.
-
B.
Delhi Assembly constituency
A Delhi Assembly constituency is a geographically defined electoral division within the National Capital Territory of Delhi that elects one representative to the Delhi Legislative Assembly.
-
C.
Delhi Legislative Assembly constituency
A Delhi Legislative Assembly constituency is a defined territorial unit within the National Capital Territory of Delhi that elects one representative (Member of the Legislative Assembly) to the Delhi Legislative Assembly.
-
D.
Madhya Pradesh Legislative Assembly constituency
A Madhya Pradesh Legislative Assembly constituency is a defined territorial electoral division within the Indian state of Madhya Pradesh that elects one member to the state's legislative assembly.
-
E.
Haryana Legislative Assembly constituency
A Haryana Legislative Assembly constituency is a defined territorial unit within the Indian state of Haryana that elects one representative (MLA) to the Haryana 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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
Created at: April 26, 2026, 8:58 p.m.