Triple
T20104965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malvi people |
E490143
|
entity |
| Predicate | hasDialect |
P4251
|
FINISHED |
| Object | Ujjaini Malvi |
—
|
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: Ujjaini Malvi | Statement: [Malvi people, hasDialect, Ujjaini Malvi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ujjaini Malvi Context triple: [Malvi people, hasDialect, Ujjaini Malvi]
-
A.
Ujjaini Malvi
chosen
Ujjaini Malvi is a regional dialect of the Malvi language spoken primarily in and around the city of Ujjain in the Indian state of Madhya Pradesh.
-
B.
Sondhwari Malvi
Sondhwari Malvi is a regional dialect of the Malvi language spoken in parts of central India.
-
C.
Rajawari Malvi
Rajawari Malvi is a regional dialect of the Malvi language spoken in parts of central India.
-
D.
Bhoyari Malvi
Bhoyari Malvi is a regional dialect of the Malvi language spoken by communities in parts of central India.
-
E.
Jain Maharashtri
Jain Maharashtri is a literary variety of the Prakrit language historically used in Jain religious texts and inscriptions.
- 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e666daf73c819089f02ca6faa2c283 |
completed | April 20, 2026, 5:48 p.m. |
Created at: April 11, 2026, 11:28 p.m.