Triple
T18887162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ellichpur |
E461985
|
entity |
| Predicate | modernSuccessor |
P3901
|
FINISHED |
| Object | Achalpur |
—
|
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: Achalpur | Statement: [Ellichpur, modernSuccessor, Achalpur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Achalpur Context triple: [Ellichpur, modernSuccessor, Achalpur]
-
A.
Achalpur
chosen
Achalpur is a historic town in Maharashtra, India, known as one of the oldest cities in the Vidarbha region.
-
B.
Shankarpur
Shankarpur is a quiet seaside village and emerging beach destination on the Bay of Bengal in West Bengal, India, known for its fishing harbor and relatively uncrowded shoreline.
-
C.
Alirajpur
Alirajpur is a town and district headquarters in western Madhya Pradesh, India, known for its predominantly tribal population and vibrant indigenous culture.
-
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.
Bhagwanpur
Bhagwanpur is a legislative assembly constituency in the Haridwar district of Uttarakhand, India.
- 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c4777434819098850da0ee1c6b43 |
completed | April 20, 2026, 6:15 a.m. |
Created at: April 10, 2026, 11:58 a.m.