Triple
T18693281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alandi |
E457051
|
entity |
| Predicate | processionTo |
P6086
|
FINISHED |
| Object | Pandharpur |
—
|
NE NERFINISHED |
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: Pandharpur | Statement: [Alandi, processionTo, Pandharpur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pandharpur Context triple: [Alandi, processionTo, Pandharpur]
-
A.
Pandharpur
chosen
Pandharpur is a major pilgrimage town in Maharashtra, India, renowned for its Vitthal (Vithoba) temple and its central role in the Bhakti movement.
-
B.
Shirdi
Shirdi is a prominent pilgrimage town in Maharashtra, India, best known as the home and shrine of the revered saint Sai Baba.
-
C.
Mahadevapura
Mahadevapura is a rapidly developing residential and commercial neighborhood in eastern Bengaluru, India, known for its proximity to major IT parks and tech hubs.
-
D.
Vithalwadi
Vithalwadi is a suburban railway station in the Mumbai metropolitan area that serves local commuters on the Central Line.
-
E.
Rajapur
Rajapur is a town in the Chitrakoot district of Uttar Pradesh, India, known for its religious significance and proximity to sites associated with the epic Ramayana.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e562e581f48190997d279296a31e7f |
completed | April 19, 2026, 11:19 p.m. |
Created at: April 10, 2026, 11:49 a.m.