Triple
T11591532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maheshwar Dam |
E274893
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Maheshwar town |
E269512
|
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: Maheshwar town | Statement: [Maheshwar Dam, locatedNear, Maheshwar town]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Maheshwar town Context triple: [Maheshwar Dam, locatedNear, Maheshwar town]
-
A.
Maheshwar
chosen
Maheshwar is a historic temple town on the banks of the Narmada River in Madhya Pradesh, India, renowned for its ghats, fort, and traditional handwoven Maheshwari sarees.
-
B.
Shelkar town
Shelkar town is a settlement in Tibet that serves as an important local center within Tingri County, known historically as a stop along routes to Mount Everest and other Himalayan regions.
-
C.
Bhagwanpur
Bhagwanpur is a legislative assembly constituency in the Haridwar district of Uttarakhand, India.
-
D.
Tekanpur
Tekanpur is a town in Madhya Pradesh, India, best known for hosting the Border Security Force’s main training academy.
-
E.
Kundalpur
Kundalpur is a historically significant Jain pilgrimage site in India, revered as the birthplace of Lord Mahavira.
- 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d894643ae48190837502b713f5b9c6 |
completed | April 10, 2026, 6:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ef1307da188190918d0f50b2fd37fa |
completed | April 27, 2026, 7:40 a.m. |
Created at: April 8, 2026, 9:38 p.m.