Triple

T20937671
Position Surface form Disambiguated ID Type / Status
Subject Chhatarpur State E515628 entity
Predicate hasBorderWith P224 FINISHED
Object Ajaigarh 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: Ajaigarh State | Statement: [Chhatarpur State, hasBorderWith, Ajaigarh State]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ajaigarh State
Context triple: [Chhatarpur State, hasBorderWith, Ajaigarh State]
  • A. Ajaigarh State chosen
    Ajaigarh State was a former princely state in British India, located in what is now central India and ruled by a local dynasty under indirect colonial administration.
  • B. Narsinghgarh State
    Narsinghgarh State was a former princely state in central India, historically ruled by local royalty under British suzerainty.
  • C. Jhalawar State
    Jhalawar State was a princely state in British India, located in the southeastern part of present-day Rajasthan and ruled by Jhala Rajput rulers.
  • D. Mundhar State
    Mundhar State was a small princely hill state located in the Simla Hills region of colonial India.
  • E. Alirajpur State
    Alirajpur State was a former princely state in colonial India, located in what is now Madhya Pradesh and ruled by local Rajput chiefs under British suzerainty.
  • 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.