Triple
T10191896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dholpur |
E238055
|
entity |
| Predicate | formerName |
P65
|
FINISHED |
| Object | Dhaulpur |
E238055
|
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: Dhaulpur | Statement: [Dholpur, formerName, Dhaulpur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dhaulpur Context triple: [Dholpur, formerName, Dhaulpur]
-
A.
Dholpur
chosen
Dholpur is a city in the Indian state of Rajasthan, known for its red sandstone, historical forts, and location near the Chambal ravines.
-
B.
Achalpur
Achalpur is a historic town in Maharashtra, India, known as one of the oldest cities in the Vidarbha region.
-
C.
Rajpura
Rajpura is an industrial and commercial town in the Patiala district of Punjab, India, known for its manufacturing base and strategic location as a transport hub.
-
D.
Anupgarh
Anupgarh is a town in the Ganganagar district of Rajasthan, India, known for its agricultural surroundings and proximity to the India–Pakistan border.
-
E.
Pratapgarh
Pratapgarh is a town in the Indian state of Rajasthan known for its historical association with the Mewar region and its distinctive tribal culture and handicrafts.
- 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_69ca84de1b208190bf17bb305b002605 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdedc4fb808190aae2e4b84be96f83 |
completed | April 2, 2026, 4:17 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d6a7d465bc8190b419de253616b0fd |
completed | April 8, 2026, 7:09 p.m. |
Created at: March 30, 2026, 9:13 p.m.