Triple
T15043424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mithi |
E379161
|
entity |
| Predicate | hasLanguage |
P15
|
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: [Mithi, hasLanguage, Dhatki]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dhatki Context triple: [Mithi, hasLanguage, 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.
Jhakri
Jhakri is a small town in Himachal Pradesh, India, known primarily for its proximity to the Nathpa Jhakri hydroelectric dam on the Sutlej River.
-
C.
Khadki
Khadki is the historical name of the Indian city now known as Aurangabad in Maharashtra.
-
D.
Bhokar
Bhokar is a legislative assembly constituency in the Nanded district of Maharashtra, India.
-
E.
Ghatanji
Ghatanji is a town in the Yavatmal district of Maharashtra, India, known for its local markets and surrounding agricultural 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded82f73208190bb55fa6b20074e27 |
completed | April 15, 2026, 12:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe9de54380819084568664b63322d2 |
completed | May 9, 2026, 2:37 a.m. |
Created at: April 10, 2026, 3 a.m.