Triple

T11851431
Position Surface form Disambiguated ID Type / Status
Subject Dausa E281916 entity
Predicate regionLanguage P10892 FINISHED
Object Dhundhari E56905 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: Dhundhari | Statement: [Dausa, regionLanguage, Dhundhari]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dhundhari
Context triple: [Dausa, regionLanguage, Dhundhari]
  • A. Dhundhari chosen
    Dhundhari is an Indo-Aryan language spoken primarily in and around Jaipur and adjoining regions of Rajasthan, India.
  • B. Dhundhar
    Dhundhar is a historical region in eastern Rajasthan, India, centered around Jaipur and known for its rich Rajput heritage and cultural significance.
  • C. Dudhrej
    Dudhrej is a town in the Surendranagar district of Gujarat, India, known for its residential areas and proximity to the city of Surendranagar.
  • D. Bhokar
    Bhokar is a legislative assembly constituency in the Nanded district of Maharashtra, India.
  • E. Bhabra
    Bhabra is a town in the Alirajpur district of Madhya Pradesh, India, known as the birthplace of Indian revolutionary Chandra Shekhar Azad.
  • 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_69d6ab287ba48190a5178779fd19b9b7 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8a65db52c8190a218736da17d0153 completed April 10, 2026, 7:27 a.m.
NED1 Entity disambiguation (via context triple) batch_69f4716d92c881908d45cb7b3babb1f7 completed May 1, 2026, 9:25 a.m.
Created at: April 8, 2026, 9:43 p.m.