Triple
T12226900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Palkhed |
E291374
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Palkhed |
E291374
|
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: Palkhed | Statement: [Battle of Palkhed, locatedIn, Palkhed]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Palkhed Context triple: [Battle of Palkhed, locatedIn, Palkhed]
-
A.
Palkhed
chosen
Palkhed is a village in Maharashtra, India, historically notable as the site of the 1728 Battle of Palkhed between the Maratha Empire and the Nizam of Hyderabad.
-
B.
Khandala
Khandala is a popular hill station in Maharashtra, India, known for its scenic valleys, waterfalls, and trekking spots in the Western Ghats.
-
C.
Khanapur
Khanapur is a town in the Indian state of Karnataka known for its scenic surroundings, forested areas, and proximity to the Western Ghats.
-
D.
Chandwad
Chandwad is a town in the Nashik district of Maharashtra, India, known for its historical temples and hill forts.
-
E.
Bhusawal
Bhusawal is a major railway and commercial city in Maharashtra, India, known for its large railway junction and banana-growing region.
- 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_69d91ca2101c8190955c36704935036a |
completed | April 10, 2026, 3:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f67c60a7d081908e402c15b7e38596 |
completed | May 2, 2026, 10:36 p.m. |
Created at: April 8, 2026, 9:51 p.m.