Triple

T20180434
Position Surface form Disambiguated ID Type / Status
Subject Bagelkhand Agency E492711 entity
Predicate hasPrincelyState P74995 FINISHED
Object Bihat State
Bihat State was a small princely state in colonial India that formed part of the Bagelkhand Agency under British rule.
 E1366662 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: Bihat State | Statement: [Bagelkhand Agency, hasPrincelyState, Bihat State]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Bihat State
Context triple: [Bagelkhand Agency, hasPrincelyState, Bihat State]
  • A. Jaora State
    Jaora State was a princely state in British India, located in what is now Madhya Pradesh and ruled by a Muslim dynasty under British suzerainty.
  • B. 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.
  • C. Tharoch State
    Tharoch State was a small princely hill state in the Simla Hills region of colonial India, ruled by local chiefs under British suzerainty.
  • D. Nabha State
    Nabha State was a princely state in colonial India, ruled by a Sikh dynasty and located in the Punjab region.
  • E. Sohawal State
    Sohawal State was a small princely state in central India that formed part of the Bagelkhand Agency during the British Raj.
  • 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: Bihat State
Triple: [Bagelkhand Agency, hasPrincelyState, Bihat State]
Generated description
Bihat State was a small princely state in colonial India that formed part of the Bagelkhand Agency under British rule.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Bihat State
Target entity description: Bihat State was a small princely state in colonial India that formed part of the Bagelkhand Agency under British rule.
  • A. Jaora State
    Jaora State was a princely state in British India, located in what is now Madhya Pradesh and ruled by a Muslim dynasty under British suzerainty.
  • B. 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.
  • C. Tharoch State
    Tharoch State was a small princely hill state in the Simla Hills region of colonial India, ruled by local chiefs under British suzerainty.
  • D. Nabha State
    Nabha State was a princely state in colonial India, ruled by a Sikh dynasty and located in the Punjab region.
  • E. Sohawal State chosen
    Sohawal State was a small princely state in central India that formed part of the Bagelkhand Agency during the British Raj.
  • F. None of above.

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_69da6268a034819081cbd9ea5a1c9475 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e668edf27881909820f9103e72533e completed April 20, 2026, 5:57 p.m.
NED1 Entity disambiguation (via context triple) batch_6a08693f41748190af0f3e86366da3c7 completed May 16, 2026, 12:55 p.m.
NEDg Description generation batch_6a086d16771c819088a5e5f34e927611 completed May 16, 2026, 1:11 p.m.
NED2 Entity disambiguation (via description) batch_6a086e5854748190a302ff625f2eb9bd completed May 16, 2026, 1:17 p.m.
Created at: April 11, 2026, 11:36 p.m.