Triple

T2686403
Position Surface form Disambiguated ID Type / Status
Subject Sikar E57493 entity
Predicate hasCulturalRegion P1968 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, hasCulturalRegion, Shekhawati]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shekhawati
Context triple: [Sikar, hasCulturalRegion, 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. 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.
  • D. 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.
  • E. 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.
  • 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_69ab4a5028388190a36f3baf1588309e completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abd9ef2fe0819082bbe746ca682a7e completed March 7, 2026, 7:55 a.m.
NED1 Entity disambiguation (via context triple) batch_69afaf5b19b88190982a669501463fa9 completed March 10, 2026, 5:42 a.m.
Created at: March 6, 2026, 9:54 p.m.