Triple
T4456447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thari |
E97736
|
entity |
| Predicate | closelyRelatedTo |
P37
|
FINISHED |
| Object | Dhatki |
E161538
|
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: Dhatki | Statement: [Thari, closelyRelatedTo, Dhatki]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dhatki Context triple: [Thari, closelyRelatedTo, Dhatki]
-
A.
Dhatki
chosen
Dhatki is an Indo-Aryan language variety spoken primarily in parts of Rajasthan, India, and neighboring regions of Pakistan, often considered a dialect within the broader Rajasthani language continuum.
-
B.
Khadki
Khadki is the historical name of the Indian city now known as Aurangabad in Maharashtra.
-
C.
Dhundhar
Dhundhar is a historical region in eastern Rajasthan, India, centered around Jaipur and known for its rich Rajput heritage and cultural significance.
-
D.
Dhundhari
Dhundhari is an Indo-Aryan language spoken primarily in and around Jaipur and adjoining regions of Rajasthan, India.
-
E.
Ghunsa
Ghunsa is a remote Himalayan village in eastern Nepal that serves as a key gateway and base for treks and expeditions around the Kangchenjunga region.
- 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_69b3454777808190b78aa9047ba1f018 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b356434e9481908f883c09e0908f6b |
completed | March 13, 2026, 12:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b6282743e08190a2c84f3b80c6d260 |
completed | March 15, 2026, 3:31 a.m. |
Created at: March 12, 2026, 11:33 p.m.