Triple
T11335906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amer |
E268469
|
entity |
| Predicate | historicalRegion |
P915
|
FINISHED |
| Object | Dhundhar |
E58269
|
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: Dhundhar | Statement: [Amer, historicalRegion, Dhundhar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dhundhar Context triple: [Amer, historicalRegion, Dhundhar]
-
A.
Dhundhar
chosen
Dhundhar is a historical region in eastern Rajasthan, India, centered around Jaipur and known for its rich Rajput heritage and cultural significance.
-
B.
Dhundhari
Dhundhari is an Indo-Aryan language spoken primarily in and around Jaipur and adjoining regions of Rajasthan, India.
-
C.
Duhshala
Duhshala is the only daughter of King Dhritarashtra and Queen Gandhari in the Indian epic Mahabharata, known for her marriage to Jayadratha.
-
D.
Dudhrej
Dudhrej is a town in the Surendranagar district of Gujarat, India, known for its residential areas and proximity to the city of Surendranagar.
-
E.
Dholka
Dholka is a historic town in the Ahmedabad district of Gujarat, India, known for its ancient architecture and role as a regional trading center.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9ff62c88190a089dd84e2ac1d17 |
completed | April 9, 2026, 6:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e55645d8bc8190b338c05ee382d5fc |
completed | April 19, 2026, 10:25 p.m. |
Created at: April 8, 2026, 9:33 p.m.