Triple
T21625419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rajputana cultural sphere |
E533687
|
entity |
| Predicate | linguisticSphere |
P112281
|
FINISHED |
| Object | Dhundhari |
—
|
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: Dhundhari | Statement: [Rajputana cultural sphere, linguisticSphere, Dhundhari]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dhundhari Context triple: [Rajputana cultural sphere, linguisticSphere, Dhundhari]
-
A.
Dhundhari
chosen
Dhundhari is an Indo-Aryan language spoken primarily in and around Jaipur and adjoining regions of Rajasthan, India.
-
B.
Dhundhar
Dhundhar is a historical region in eastern Rajasthan, India, centered around Jaipur and known for its rich Rajput heritage and cultural significance.
-
C.
Kheralu
Kheralu is a town in the Mehsana region of Gujarat, India, known for its local markets and role as a small regional center for surrounding rural areas.
-
D.
Kherwara
Kherwara is a town in the Udaipur district of Rajasthan, India, known for its tribal population and location along key regional road routes.
-
E.
Kundarki
Kundarki is a notable town in the Moradabad district of Uttar Pradesh, India, serving as a local hub for trade and administration.
- 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef52121c3c8190b9b4d862ed247c71 |
completed | April 27, 2026, 12:09 p.m. |
Created at: April 16, 2026, 6:34 p.m.