Triple
T2614012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shekhawati |
E58842
|
entity |
| Predicate | closelyRelatedTo |
P37
|
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: [Shekhawati, closelyRelatedTo, Dhundhari]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dhundhari Context triple: [Shekhawati, closelyRelatedTo, 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.
Shivpuri
Shivpuri is a historic town and former princely state in central India, known for its forests, wildlife sanctuaries, and royal palaces.
-
D.
Singhwara
Singhwara is a town located in the Darbhanga district of the Indian state of Bihar.
-
E.
Deoli
Deoli is a town in the Indian state of Maharashtra, situated within the Wardha district and known for its agricultural surroundings and local trade.
- 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_69ab4ac444dc819099614e534dd6021f |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd87dcfbc8190b264062002bfe4ba |
completed | March 7, 2026, 7:49 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afa04b00908190b42f0ed753009c42 |
completed | March 10, 2026, 4:38 a.m. |
Created at: March 6, 2026, 9:50 p.m.