Triple
T5504838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhili languages |
E144413
|
entity |
| Predicate | hasDialect |
P4251
|
FINISHED |
| Object | Panchmahali 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: Panchmahali Bhili | Statement: [Bhili languages, hasDialect, Panchmahali Bhili]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Panchmahali Bhili Context triple: [Bhili languages, hasDialect, Panchmahali Bhili]
-
A.
Bhils
The Bhils are one of central India's largest indigenous Adivasi communities, known for their distinct language, rich folk traditions, and close association with forest and agrarian livelihoods.
-
B.
Bhili
chosen
Bhili is an Indo-Aryan language spoken primarily by the Bhil tribal communities in western and central India.
-
C.
Kolami
Kolami is a Dravidian language spoken primarily by the Kolam tribal communities in central India, especially in parts of Maharashtra and Telangana.
-
D.
Lambadi
Lambadi is an Indo-Aryan language variety spoken primarily by the Lambadi (Banjara) community across parts of northwestern and central India.
-
E.
Aheri Gondi
Aheri Gondi is a regional variety of the Southern Gondi language spoken by Gondi communities in parts of central 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_69c008f6b5048190a09064116062cf69 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f0e91d08190a4db907030955bb3 |
completed | March 22, 2026, 4:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c059c9a99881909863a0d1b061df72 |
completed | March 22, 2026, 9:06 p.m. |
Created at: March 22, 2026, 3:32 p.m.