Triple
T23395416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Khandesh district |
E559343
|
entity |
| Predicate | presentDayMajorCity |
P48921
|
FINISHED |
| Object | Chalisgaon |
—
|
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: Chalisgaon | Statement: [East Khandesh district, presentDayMajorCity, Chalisgaon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Chalisgaon Context triple: [East Khandesh district, presentDayMajorCity, Chalisgaon]
-
A.
Chalisgaon
chosen
Chalisgaon is a town in the Indian state of Maharashtra known for its railway junction and proximity to historical and religious sites.
-
B.
Krishnanagar
Krishnanagar is a historic town in eastern India known for its cultural heritage, temples, and traditional clay artistry.
-
C.
Santipur
Santipur is a historic town in West Bengal, India, renowned for its traditional handloom sarees and cultural heritage.
-
D.
Garhgaon
Garhgaon was a historic city in Assam, India, that served as an important political and administrative center of the Ahom dynasty.
-
E.
Mahidpur
Mahidpur is a historic town in the Indian state of Madhya Pradesh, known for its location in the Malwa region and its role in the Anglo-Maratha conflicts.
- 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_69e24549610c8190a069d6411ce5f661 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a4db1c888190ace5d58bcc8645c1 |
completed | April 29, 2026, 6:27 a.m. |
Created at: April 17, 2026, 5:36 p.m.