Triple
T6967770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kauravi |
E161530
|
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: [Kauravi, hasAlternativeName, Kauravi Hindi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kauravi Hindi Context triple: [Kauravi, 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.
Bhairavi
Bhairavi is a fierce and transformative Hindu goddess associated with destruction, time, and spiritual awakening, revered as one of the ten Mahavidyas in Shakta tradition.
-
C.
Baleswari Odia
Baleswari Odia is a regional variety of the Odia language spoken primarily in the Balasore (Baleswar) region of Odisha, India.
-
D.
Kesari
Kesari is a figure in Hindu mythology known as the vanara chief and father of the deity Hanuman.
-
E.
Rajawari Malvi
Rajawari Malvi is a regional dialect of the Malvi language spoken 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_69c68853cff881908439d488924a8283 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db1373d88190967b42630f8688d6 |
completed | March 27, 2026, 7:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c76195e69c8190a8f7d9ca223a96e6 |
completed | March 28, 2026, 5:05 a.m. |
Created at: March 27, 2026, 2:30 p.m.