Triple

T2877227
Position Surface form Disambiguated ID Type / Status
Subject Dhundhari E56905 entity
Predicate alternateName P39 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: [Dhundhari, alternateName, Dhundari]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dhundari
Context triple: [Dhundhari, alternateName, 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. Kadamtala
    Kadamtala is a small settlement located on Middle Andaman Island in the Andaman and Nicobar Islands of India.
  • D. Kalgidhar
    Kalgidhar is an honorific epithet of Guru Gobind Singh, emphasizing his revered status as a timeless, divine protector in Sikh tradition.
  • E. Shivpuri
    Shivpuri is a historic town and former princely state in central India, known for its forests, wildlife sanctuaries, and royal palaces.
  • 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_69ab4a4ced288190ab6d3e062d10f7f6 completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abe007329c8190b0bc1851c7307124 completed March 7, 2026, 8:21 a.m.
NED1 Entity disambiguation (via context triple) batch_69b03158d0ec8190ba9675ece8f62033 completed March 10, 2026, 2:57 p.m.
Created at: March 6, 2026, 10:03 p.m.