Triple

T11335922
Position Surface form Disambiguated ID Type / Status
Subject Amer E268469 entity
Predicate languageRegional P10892 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: [Amer, languageRegional, Rajasthani]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rajasthani
Context triple: [Amer, languageRegional, 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_69d6aacb1f0881908c84a349fd1be047 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e9ff62c88190a089dd84e2ac1d17 completed April 9, 2026, 6:03 p.m.
NED1 Entity disambiguation (via context triple) batch_69e5263cce588190a91f91cbdf023d5e completed April 19, 2026, 7 p.m.
Created at: April 8, 2026, 9:33 p.m.