Triple

T8658231
Position Surface form Disambiguated ID Type / Status
Subject Bikaner division E205475 entity
Predicate language P15 FINISHED
Object Rajasthani E31770 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: Rajasthani | Statement: [Bikaner division, language, Rajasthani]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rajasthani
Context triple: [Bikaner division, language, Rajasthani]
  • A. Rajasthani chosen
    Rajasthani is an Indo-Aryan language (or group of dialects) spoken primarily in the Indian state of Rajasthan and surrounding regions.
  • B. Rajasthani people
    Rajasthani people are an ethnolinguistic group from the Indian state of Rajasthan, known for their distinct languages, vibrant folk culture, and rich historical heritage of Rajput kingdoms and desert traditions.
  • C. Shekhawati
    Shekhawati is a dialect of the Rajasthani language spoken primarily in the Shekhawati region of northern Rajasthan, India.
  • D. Chhattisgarhi
    Chhattisgarhi is an Indo-Aryan language spoken primarily in the Indian state of Chhattisgarh and surrounding regions.
  • E. Bagheli
    Bagheli is an Indo-Aryan language spoken primarily in the Bagelkhand region of central India, closely related to Hindi and used by millions as a regional vernacular.
  • 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_69ca8350897c819086cde7596fbe5fe7 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc486d576081908ad28749c7971432 completed March 31, 2026, 10:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69ceccec941881908263cd3205f10ccd completed April 2, 2026, 8:09 p.m.
Created at: March 30, 2026, 6:30 p.m.