Triple
T21266333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gandhinagar North |
E524137
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Gujarat Legislative Assembly constituency |
C44443
|
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: Gujarat Legislative Assembly constituency Context triple: [Gandhinagar North, instanceOf, Gujarat Legislative Assembly constituency]
-
A.
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.
-
B.
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.
-
C.
Punjab Legislative Assembly constituency
A Punjab Legislative Assembly constituency is a defined territorial unit within the Indian state of Punjab that elects one representative (MLA) to the Punjab Legislative Assembly.
-
D.
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.
-
E.
Andhra Pradesh Legislative Assembly constituency
An Andhra Pradesh Legislative Assembly constituency is a geographically defined electoral division within the Indian state of Andhra Pradesh that elects one member to the Andhra Pradesh Legislative Assembly.
- F. None of above. chosen
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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 4 p.m.