Triple
T23395417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Khandesh district |
E559343
|
entity |
| Predicate | presentDayMajorCity |
P48921
|
FINISHED |
| Object | Pachora |
—
|
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: Pachora | Statement: [East Khandesh district, presentDayMajorCity, Pachora]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pachora Context triple: [East Khandesh district, presentDayMajorCity, Pachora]
-
A.
Pachora
chosen
Pachora is a town in the Jalgaon district of Maharashtra, India, known as a local commercial and agricultural center in the region.
-
B.
Dahanapura
Dahanapura was the principal city and political center of the historical Kediri Kingdom in Java.
-
C.
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.
-
D.
Badami
Badami is a historic town in Karnataka, India, renowned for its rock-cut cave temples and ancient Chalukyan architecture.
-
E.
Pravarapura
Pravarapura was an ancient city in central India that served as a major political and cultural center under the Vakataka dynasty.
- 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.