Triple
T18837183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhili |
E460693
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Bhilboli |
—
|
NE NERFINISHED |
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: Bhilboli | Statement: [Bhili, hasAlternativeName, Bhilboli]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bhilboli Context triple: [Bhili, hasAlternativeName, Bhilboli]
-
A.
Bhilodi
chosen
Bhilodi is an alternative name for Bhili, an Indo-Aryan language spoken primarily by the Bhil people of western and central India.
-
B.
Bhili
Bhili is an Indo-Aryan language spoken primarily by the Bhil tribal communities in western and central India.
-
C.
Shivpuri
Shivpuri is a historic town and former princely state in central India, known for its forests, wildlife sanctuaries, and royal palaces.
-
D.
Chiplun
Chiplun is a town in Maharashtra, India, situated along the Vashishti River and known as a commercial and transport hub in the Konkan region.
-
E.
Ghansoli
Ghansoli is a rapidly developing residential and commercial node in Navi Mumbai, Maharashtra, known for its growing IT parks, educational institutions, and connectivity to Mumbai via rail and road.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a99e86388190957acaaab401b5cb |
completed | April 20, 2026, 4:20 a.m. |
Created at: April 10, 2026, 11:56 a.m.