Triple
T18837218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wagdi |
E460694
|
entity |
| Predicate | closelyRelatedTo |
P37
|
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: [Wagdi, closelyRelatedTo, Bhili]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bhili Context triple: [Wagdi, closelyRelatedTo, Bhili]
-
A.
Bhili
chosen
Bhili is an Indo-Aryan language spoken primarily by the Bhil tribal communities in western and central India.
-
B.
Bhadraba
Bhadraba is a month in the traditional Hindu lunar calendar, roughly corresponding to August–September in the Gregorian calendar.
-
C.
Paharia
Paharia is an alternative name for the Malto language, a Dravidian language spoken primarily by tribal communities in eastern India.
-
D.
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.
-
E.
Dhundhari
Dhundhari is an Indo-Aryan language spoken primarily in and around Jaipur and adjoining regions of Rajasthan, 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a99e86388190957acaaab401b5cb |
completed | April 20, 2026, 4:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0582a3bd7881908dcd97ece5f576a8 |
completed | May 14, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.