Triple

T20737342
Position Surface form Disambiguated ID Type / Status
Subject Rajgarh State E509744 entity
Predicate hasBorderWith P224 FINISHED
Object Khilchipur State
Khilchipur State was a former princely state in British India located in the central Indian region near present-day Madhya Pradesh.
 E1449302 NE FINISHED

How this triple was built (4 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: Khilchipur State | Statement: [Rajgarh State, hasBorderWith, Khilchipur State]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Khilchipur State
Context triple: [Rajgarh State, hasBorderWith, Khilchipur State]
  • A. Baraundha State
    Baraundha State was a former princely state in British India located in the Bagelkhand region, ruled by local royalty under indirect colonial administration.
  • B. Mundhar State
    Mundhar State was a small princely hill state located in the Simla Hills region of colonial India.
  • C. Bijawar State
    Bijawar State was a former princely state in British India, located in the Bundelkhand region of present-day Madhya Pradesh.
  • D. Chhatarpur State
    Chhatarpur State was a princely state in British India, located in the Bundelkhand region and ruled by a local dynasty under British suzerainty.
  • E. Rajpipla State
    Rajpipla State was a former princely state in British India, located in present-day Gujarat.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Khilchipur State
Triple: [Rajgarh State, hasBorderWith, Khilchipur State]
Generated description
Khilchipur State was a former princely state in British India located in the central Indian region near present-day Madhya Pradesh.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Khilchipur State
Target entity description: Khilchipur State was a former princely state in British India located in the central Indian region near present-day Madhya Pradesh.
  • A. Baraundha State
    Baraundha State was a former princely state in British India located in the Bagelkhand region, ruled by local royalty under indirect colonial administration.
  • B. Mundhar State
    Mundhar State was a small princely hill state located in the Simla Hills region of colonial India.
  • C. Bijawar State
    Bijawar State was a former princely state in British India, located in the Bundelkhand region of present-day Madhya Pradesh.
  • D. Chhatarpur State
    Chhatarpur State was a princely state in British India, located in the Bundelkhand region and ruled by a local dynasty under British suzerainty.
  • E. Rajpipla State
    Rajpipla State was a former princely state in British India, located in present-day Gujarat.
  • F. None of above. chosen

Provenance (5 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_69e0b4c589c08190834fb5d86d0efa2b completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c20ac6e881908524be890be699e7 completed April 21, 2026, 12:17 a.m.
NED1 Entity disambiguation (via context triple) batch_6a08ef7deae081908657d2ef8a2445da completed May 16, 2026, 10:28 p.m.
NEDg Description generation batch_6a08f127ec5c819093407df681fab39e completed May 16, 2026, 10:35 p.m.
NED2 Entity disambiguation (via description) batch_6a08f1ba42288190806c924a14043b30 completed May 16, 2026, 10:37 p.m.
Created at: April 16, 2026, 12:32 p.m.