Triple

T20180424
Position Surface form Disambiguated ID Type / Status
Subject Bagelkhand Agency E492711 entity
Predicate hasPrincelyState P74995 FINISHED
Object Sohawal 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: Sohawal State | Statement: [Bagelkhand Agency, hasPrincelyState, Sohawal State]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sohawal State
Context triple: [Bagelkhand Agency, hasPrincelyState, Sohawal State]
  • A. Sohawal State chosen
    Sohawal State was a small princely state in central India that formed part of the Bagelkhand Agency during the British Raj.
  • B. Nabha State
    Nabha State was a princely state in colonial India, ruled by a Sikh dynasty and located in the Punjab region.
  • C. Gondal State
    Gondal State was a princely state in western India, located in present-day Gujarat, known for its progressive reforms and modern infrastructure under its royal rulers.
  • D. 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.
  • E. 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.
  • 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_69da6268a034819081cbd9ea5a1c9475 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e668edf27881909820f9103e72533e completed April 20, 2026, 5:57 p.m.
Created at: April 11, 2026, 11:36 p.m.