Triple

T1617434
Position Surface form Disambiguated ID Type / Status
Subject Jaisalmer E34751 entity
Predicate additionalOfficialLanguage P5601 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: [Jaisalmer, additionalOfficialLanguage, Rajasthani]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rajasthani
Context triple: [Jaisalmer, additionalOfficialLanguage, 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. Shekhawati
    Shekhawati is a dialect of the Rajasthani language spoken primarily in the Shekhawati region of northern Rajasthan, India.
  • C. Chhattisgarhi
    Chhattisgarhi is an Indo-Aryan language spoken primarily in the Indian state of Chhattisgarh and surrounding regions.
  • D. 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.
  • E. Sarnami Hindustani
    Sarnami Hindustani is a Hindi–Bhojpuri-based Indo-Aryan language developed among Indo-Caribbean communities, particularly in Suriname, from the speech of Indian indentured laborers.
  • 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_69a885ffc5ec819091afa325d5f9611c completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a909abbec081908f95547471530ad5 completed March 5, 2026, 4:42 a.m.
NED1 Entity disambiguation (via context triple) batch_69ad51cf7b7c8190847ab6795fb5613b completed March 8, 2026, 10:39 a.m.
Created at: March 4, 2026, 7:28 p.m.