Triple
T5040340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malvi |
E113527
|
entity |
| Predicate | closelyRelatedTo |
P37
|
FINISHED |
| Object | Rajasthani |
E31770
|
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: Rajasthani | Statement: [Malvi, closelyRelatedTo, Rajasthani]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rajasthani Context triple: [Malvi, closelyRelatedTo, Rajasthani]
-
A.
Rajasthani
chosen
Rajasthani is an Indo-Aryan language (or group of dialects) spoken primarily in the Indian state of Rajasthan and surrounding regions.
-
B.
Shekhawati
Shekhawati is a dialect of the Rajasthani language spoken primarily in the Shekhawati region of northern Rajasthan, India.
-
C.
Chhattisgarhi
Chhattisgarhi is an Indo-Aryan language spoken primarily in the Indian state of Chhattisgarh and surrounding regions.
-
D.
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.
-
E.
Sarnami Hindustani
Sarnami Hindustani is a Hindi–Bhojpuri-based Indo-Aryan language developed among Indo-Caribbean communities, particularly in Suriname, from the speech of Indian indentured laborers.
- 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_69bd44384298819089c49e7c330ec7b8 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73dd27fc8190817e53311ea3f706 |
completed | March 20, 2026, 4:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be9c8084388190b25bbffc42f0b3ed |
completed | March 21, 2026, 1:26 p.m. |
Created at: March 20, 2026, 1:37 p.m.