Triple

T31706517
Position Surface form Disambiguated ID Type / Status
Subject Haridwar Rural E809195 entity
Predicate instanceOf P0 FINISHED
Object Uttarakhand Legislative Assembly constituency C57579 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: Uttarakhand Legislative Assembly constituency
Context triple: [Haridwar Rural, instanceOf, Uttarakhand Legislative Assembly constituency]
  • A. 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.
  • B. 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.
  • C. 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.
  • 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. 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.
  • 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_69f348de914081909fc8edff56f34dbe completed April 30, 2026, 12:19 p.m.
Created at: April 30, 2026, 11:14 p.m.