Triple

T11976603
Position Surface form Disambiguated ID Type / Status
Subject Dausa district E285055 entity
Predicate widelySpokenLanguage P2266 FINISHED
Object Dhundari 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: Dhundari | Statement: [Dausa district, widelySpokenLanguage, Dhundari]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dhundari
Context triple: [Dausa district, widelySpokenLanguage, Dhundari]
  • 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. Bhailsa
    Bhailsa is the former historical name of Vidisha, an ancient city in the central Indian state of Madhya Pradesh known for its rich archaeological and cultural heritage.
  • D. Dharni
    Dharni is a small town in the Amravati district of Maharashtra, India, known as a local administrative and market center for surrounding rural and tribal areas.
  • E. Bhokar
    Bhokar is a legislative assembly constituency in the Nanded district of Maharashtra, India.
  • 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_69d6ab2eaeb881909f7914758f859413 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d903926690819090e7ce982f103457 completed April 10, 2026, 2:05 p.m.
NED1 Entity disambiguation (via context triple) batch_69f49d0791348190a2f6c0e808af3aea completed May 1, 2026, 12:31 p.m.
Created at: April 8, 2026, 9:46 p.m.