Triple

T12386711
Position Surface form Disambiguated ID Type / Status
Subject Sikar district E295884 entity
Predicate region P40 FINISHED
Object Shekhawati E58842 NE FINISHED

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: Shekhawati | Statement: [Sikar district, region, Shekhawati]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shekhawati
Context triple: [Sikar district, region, Shekhawati]
  • A. Shekhawati chosen
    Shekhawati is a dialect of the Rajasthani language spoken primarily in the Shekhawati region of northern Rajasthan, India.
  • B. Kishangarh State
    Kishangarh State was a princely state in colonial India, ruled by Rajput princes and located in the region historically known as Rajputana (now largely in Rajasthan).
  • C. Maharawat
    Maharawat is a hereditary royal title historically used by the ruling monarchs of certain princely states in India, including Pratapgarh.
  • D. Bikaner State
    Bikaner State was a princely state in northwestern India, ruled by Rajput kings and centered on the city of Bikaner in present-day Rajasthan.
  • E. Jodhpur State
    Jodhpur State was a princely state in western India, ruled by the Rathore Rajput dynasty with its capital at Jodhpur, that existed under British suzerainty until Indian independence.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d6ad9e653c8190b1473c860ee53dae completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d93fbd489c819098233a111442762e completed April 10, 2026, 6:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69f671852f588190924ded1c0a360b47 completed May 2, 2026, 9:49 p.m.
Created at: April 8, 2026, 9:54 p.m.