Triple
T16528981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khadakwasla Dam |
E401512
|
entity |
| Predicate | nearLocality |
P350
|
FINISHED |
| Object | Khadakwasla |
E401496
|
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: Khadakwasla | Statement: [Khadakwasla Dam, nearLocality, Khadakwasla]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Khadakwasla Context triple: [Khadakwasla Dam, nearLocality, Khadakwasla]
-
A.
Khadakwasla
chosen
Khadakwasla is a suburban area near Pune in Maharashtra, India, known for its lake, dam, and military establishments.
-
B.
Chakdara
Chakdara is a town in Pakistan’s Khyber Pakhtunkhwa province, known as a strategic gateway to the Swat Valley and an area rich in archaeological and historical significance.
-
C.
Khandela
Khandela is a prominent town in Rajasthan, India, known historically as a local trading and cultural center in the Sikar region.
-
D.
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.
-
E.
Sakesar
Sakesar is a prominent mountain peak in Pakistan’s Punjab region, known for its scenic views, cooler climate, and strategic location within the Salt Range.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32ed57be481908625d4c5aab0940c |
completed | April 18, 2026, 7:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a006ed808448190936ea51a9a28a95a |
completed | May 10, 2026, 11:41 a.m. |
Created at: April 10, 2026, 5:14 a.m.