Triple
T12161759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purandar Fort |
E289724
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Saswad |
E295230
|
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: Saswad | Statement: [Purandar Fort, locatedNear, Saswad]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Saswad Context triple: [Purandar Fort, locatedNear, Saswad]
-
A.
Saswad
chosen
Saswad is a historic town in Maharashtra, India, known for its association with early Maratha Peshwas and several important temples and forts.
-
B.
Partapur
Partapur is a locality in Meerut district of Uttar Pradesh, India, known for its proximity to the Dr. Bhimrao Ambedkar Airstrip and its growing urban and institutional development.
-
C.
Sawai Madhopur
Sawai Madhopur is a town in Rajasthan, India, best known as the main gateway to the tiger-rich Ranthambore region and its historic fort.
-
D.
Palwal
Palwal is a city in the Indian state of Haryana that forms part of the extended urban area surrounding Delhi.
-
E.
Bahadurgarh
Bahadurgarh is a rapidly developing city in the Indian state of Haryana that forms part of the urban agglomeration surrounding Delhi.
- 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915c395e48190a16e97fd29787a51 |
completed | April 10, 2026, 3:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f61e4deb308190aa1a99a78d46b461 |
completed | May 2, 2026, 3:54 p.m. |
Created at: April 8, 2026, 9:50 p.m.