Triple
T5966660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khandesh |
E132769
|
entity |
| Predicate | language |
P15
|
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: [Khandesh, language, Bhili]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bhili Context triple: [Khandesh, language, 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.
Mahoba
Mahoba is a historic town in Uttar Pradesh, India, renowned for its role as a prominent center of power and culture in the Bundelkhand region, especially under the Chandela rulers.
-
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_69c0086c2364819091e9fe2f58fa2517 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03a3e06848190b1d1a191db257a07 |
completed | March 22, 2026, 6:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0e3ff62f08190be56bb9c450c9647 |
completed | March 23, 2026, 6:55 a.m. |
Created at: March 22, 2026, 4:03 p.m.