Triple

T20937669
Position Surface form Disambiguated ID Type / Status
Subject Chhatarpur State E515628 entity
Predicate hasBorderWith P224 FINISHED
Object Panna State NE NERFINISHED

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: Panna State | Statement: [Chhatarpur State, hasBorderWith, Panna State]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Panna State
Context triple: [Chhatarpur State, hasBorderWith, Panna State]
  • A. Panna State chosen
    Panna State was a former princely state in central India, historically ruled by Bundela Rajputs and known for its diamond mines and later incorporation into the Indian Union.
  • B. Chamba State
    Chamba State was a former princely state in the western Himalayas of British India, known for its mountainous terrain, historic temples, and distinctive Pahari art and culture.
  • C. Mewar State
    Mewar State was a historic princely state in present-day Rajasthan, India, centered on the city of Udaipur and ruled for centuries by the Sisodia Rajput dynasty.
  • D. Pahra State
    Pahra State was a small princely state in British India that formed part of the Bagelkhand Agency in Central India.
  • E. Bija State
    Bija State was a small princely state in colonial India that formed part of the Simla Hill States group in the Himalayan region.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4fc13408190b06868df03c5c29b completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6f9534cd48190a86665fb1df6b077 completed April 21, 2026, 4:13 a.m.
Created at: April 16, 2026, 12:49 p.m.