Triple
T18692647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berar Sultanate |
E457038
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Ellichpur |
—
|
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: Ellichpur | Statement: [Berar Sultanate, capital, Ellichpur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ellichpur Context triple: [Berar Sultanate, capital, Ellichpur]
-
A.
Ellichpur
chosen
Ellichpur is a historic city in Maharashtra, India, that once served as an important regional capital under the Deccan sultanates.
-
B.
Santalpur
Santalpur is a small town in the Patan district of Gujarat, India, known primarily as a local administrative and trading center for surrounding rural areas.
-
C.
Karanpur
Karanpur is a town located in the Ganganagar district of the northern Indian state of Rajasthan.
-
D.
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.
-
E.
Jagdishpur
Jagdishpur is a town in the Amethi district of Uttar Pradesh, India, known for its industrial area and historical significance in the region.
- 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_69e562e4756881909335e1e7b3c23e28 |
completed | April 19, 2026, 11:19 p.m. |
Created at: April 10, 2026, 11:49 a.m.