Triple
T11589264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khargone district |
E274834
|
entity |
| Predicate | commonlySpokenLanguage |
P7445
|
FINISHED |
| Object | Bhili |
E460693
|
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: Bhili | Statement: [Khargone district, commonlySpokenLanguage, Bhili]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bhili Context triple: [Khargone district, commonlySpokenLanguage, Bhili]
-
A.
Bhili
chosen
Bhili is an Indo-Aryan language spoken primarily by the Bhil tribal communities in western and central India.
-
B.
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.
-
C.
Dhundhari
Dhundhari is an Indo-Aryan language spoken primarily in and around Jaipur and adjoining regions of Rajasthan, India.
-
D.
Kachwaha
Kachwaha is a prominent Rajput clan historically associated with the ruling dynasty of Amber and Jaipur in present-day Rajasthan, India.
-
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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d89463360c8190b91228c46bfe2e5f |
completed | April 10, 2026, 6:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e71451f1388190b72d7b755d198999 |
completed | April 21, 2026, 6:08 a.m. |
Created at: April 8, 2026, 9:38 p.m.