Triple

T19019151
Position Surface form Disambiguated ID Type / Status
Subject Najafgarh Assembly constituency E465437 entity
Predicate instanceOf P0 FINISHED
Object Delhi Legislative Assembly constituency C41524 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: Delhi Legislative Assembly constituency
Context triple: [Najafgarh Assembly constituency, instanceOf, Delhi Legislative Assembly constituency]
  • A. 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.
  • B. 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.
  • 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. former Lok Sabha constituency
    A former Lok Sabha constituency is an electoral district that once elected a representative to India’s lower house of Parliament but has since been dissolved, merged, or restructured through delimitation or administrative changes.
  • E. Puducherry Legislative Assembly constituency
    A Puducherry Legislative Assembly constituency is a territorial electoral division within the Union Territory of Puducherry, each of which elects one member to the Puducherry 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_69d8dd025c188190a1d81f5b4ec7e2c6 completed April 10, 2026, 11:20 a.m.
Created at: April 10, 2026, 12:02 p.m.