Triple
T22333607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karaikal (Puducherry Legislative Assembly) |
E552085
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | State 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 assembly constituency in India Context triple: [Karaikal (Puducherry Legislative Assembly), instanceOf, State 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.
state assembly of India
The state assembly of India is a legislative body at the state level responsible for making laws, approving budgets, and overseeing the executive within that state.
-
C.
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.
-
D.
Gujarat Legislative Assembly constituency
A Gujarat Legislative Assembly constituency is a defined electoral district within the Indian state of Gujarat from which voters elect one representative to the Gujarat Legislative Assembly.
-
E.
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.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:43 p.m.