Triple
T11687309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khandwa district |
E277775
|
entity |
| Predicate | hasNotableTown |
P14082
|
FINISHED |
| Object | Khandwa |
E114390
|
NE FINISHED |
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: Khandwa | Statement: [Khandwa district, hasNotableTown, Khandwa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Khandwa Context triple: [Khandwa district, hasNotableTown, Khandwa]
-
A.
Khandwa
chosen
Khandwa is a city in central India known as a regional commercial and cultural center in the state of Madhya Pradesh.
-
B.
Jhabua
Jhabua is a town and administrative district headquarters in western Madhya Pradesh, India, known for its significant tribal population and culture.
-
C.
Ratlam
Ratlam is a prominent commercial city in western Madhya Pradesh, India, known for its railway junction, textile and chemical industries, and production of gold and silver jewelry.
-
D.
Chandwad
Chandwad is a town in the Nashik district of Maharashtra, India, known for its historical temples and hill forts.
-
E.
Dhrol
Dhrol is a town in the Jamnagar district of Gujarat, India, known historically as the seat of the former princely Dhrol State.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4654be881909bd0256cf18e25de |
completed | April 10, 2026, 7:19 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f08fd4c09081909ee36de77ca67247 |
completed | April 28, 2026, 10:45 a.m. |
Created at: April 8, 2026, 9:40 p.m.