Triple
T1409292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khari Boli |
E31768
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Kauravi Hindi |
E161530
|
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: Kauravi Hindi | Statement: [Khari Boli, hasAlternativeName, Kauravi Hindi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kauravi Hindi Context triple: [Khari Boli, hasAlternativeName, Kauravi Hindi]
-
A.
Kauravi
chosen
Kauravi is a dialect of Hindi-Urdu historically spoken in the Delhi and western Uttar Pradesh region, considered a major basis for the standard Hindi register.
-
B.
Baleswari Odia
Baleswari Odia is a regional variety of the Odia language spoken primarily in the Balasore (Baleswar) region of Odisha, India.
-
C.
Kesari
Kesari is a figure in Hindu mythology known as the vanara chief and father of the deity Hanuman.
-
D.
Malwai Punjabi
Malwai Punjabi is a regional variety of the Punjabi language spoken primarily in the Malwa region of the Indian state of Punjab.
-
E.
Bagheli
Bagheli is an Indo-Aryan language spoken primarily in the Bagelkhand region of central India, closely related to Hindi and used by millions as a regional vernacular.
- 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3c10f44819085e1c4601423740d |
completed | March 1, 2026, 10:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad015a52a88190933e7337067e5364 |
completed | March 8, 2026, 4:55 a.m. |
Created at: March 1, 2026, 7:59 p.m.