Triple

T11851361
Position Surface form Disambiguated ID Type / Status
Subject Hoshangabad district E281914 entity
Predicate legislativeAssemblyConstituenciesInclude P23217 FINISHED
Object Pipariya E952874 NE FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Pipariya | Statement: [Hoshangabad district, legislativeAssemblyConstituenciesInclude, Pipariya]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pipariya
Context triple: [Hoshangabad district, legislativeAssemblyConstituenciesInclude, Pipariya]
  • A. Pipariya chosen
    Pipariya is a town in the Indian state of Madhya Pradesh, known as a key rail and road gateway to the nearby hill station of Pachmarhi.
  • B. Pipra
    Pipra is a genus of small, brightly colored Neotropical manakins known for the males’ elaborate courtship displays in forest understories.
  • C. Pupri
    Pupri is a small town in the Sitamarhi district of the Indian state of Bihar, known primarily as a local commercial and administrative center for surrounding rural areas.
  • D. Bhokar
    Bhokar is a legislative assembly constituency in the Nanded district of Maharashtra, India.
  • E. Paraiya
    Paraiya is a village and administrative block in Bihar, India, known as one of the community development blocks within Gaya district.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 batches)

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_69d6ab287ba48190a5178779fd19b9b7 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8a65db52c8190a218736da17d0153 completed April 10, 2026, 7:27 a.m.
NED1 Entity disambiguation (via context triple) batch_69f4583d9900819090be07726ed00b93 completed May 1, 2026, 7:37 a.m.
Created at: April 8, 2026, 9:43 p.m.