Triple
T4986839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Braj region |
E112023
|
entity |
| Predicate | containsCity |
P294
|
FINISHED |
| Object | Dholpur |
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: Dholpur | Statement: [Braj region, containsCity, Dholpur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dholpur Context triple: [Braj region, containsCity, Dholpur]
-
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.
Madhepura
Madhepura is a town and district headquarters in the eastern Indian state of Bihar, known for its agricultural economy and regional administrative importance.
-
C.
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.
-
D.
Vidisha
Vidisha is a historic city in the central Indian state of Madhya Pradesh, known for its ancient Buddhist and Hindu heritage and archaeological sites.
-
E.
Hajipur
Hajipur is a prominent city in the Indian state of Bihar, known as an important railway and commercial hub located near the state capital, Patna.
- 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_69bd441be7bc8190b530362d427b97d2 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd727c25bc8190b72f6ddd3772c80a |
completed | March 20, 2026, 4:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be8a20a8f88190980409794c90461f |
completed | March 21, 2026, 12:08 p.m. |
Created at: March 20, 2026, 1:34 p.m.