Triple
T12222953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pratapgad Fort |
E291266
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Poladpur |
E919080
|
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: Poladpur | Statement: [Pratapgad Fort, locatedNear, Poladpur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Poladpur Context triple: [Pratapgad Fort, locatedNear, Poladpur]
-
A.
Poladpur
chosen
Poladpur is a town and taluka in Maharashtra, India, known for its scenic location in the Western Ghats and proximity to popular hill stations like Mahabaleshwar.
-
B.
Bhagwanpur
Bhagwanpur is a legislative assembly constituency in the Haridwar district of Uttarakhand, India.
-
C.
Vikrampur
Vikrampur was a historic urban and political center in the Bengal region, renowned as an important seat of power and culture in medieval South Asia.
-
D.
Mahipalpur
Mahipalpur is an urban village and commercial area in Delhi, India, located near Indira Gandhi International Airport and known for its hotels, transport hubs, and proximity to major highways.
-
E.
Jagdishpur
Jagdishpur is a town in the Bhojpur district of Bihar, India, historically known as the ancestral estate of the 19th-century freedom fighter Kunwar Singh.
- 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_69d6ab668acc8190963ba424049d6aee |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91c961d648190ad6ce5f7d228eee4 |
completed | April 10, 2026, 3:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f60aa6d3d481909852a6f2f90d7a41 |
completed | May 2, 2026, 2:31 p.m. |
Created at: April 8, 2026, 9:51 p.m.