Triple
T19254087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malwa region |
E481468
|
entity |
| Predicate | hasMajorCity |
P316
|
FINISHED |
| Object | Shajapur |
—
|
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: Shajapur | Statement: [Malwa region, hasMajorCity, Shajapur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shajapur Context triple: [Malwa region, hasMajorCity, Shajapur]
-
A.
Shajapur
chosen
Shajapur is a town and administrative center in central India known for being the headquarters of Shajapur district in the state of Madhya Pradesh.
-
B.
Shirpur
Shirpur is a town in the Dhule district of Maharashtra, India, known for its educational institutions and pioneering water conservation initiatives.
-
C.
Khambhat
Khambhat is a historic coastal town in Gujarat, India, known for its ancient port, trade heritage, and distinctive gulf on the Arabian Sea.
-
D.
Bharuch
Bharuch is an ancient port city in the Indian state of Gujarat, historically significant as a major trading hub on the banks of the Narmada River.
-
E.
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.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb3339648190a87d38ce42aff016 |
completed | April 20, 2026, 10:08 a.m. |
Created at: April 10, 2026, 1:28 p.m.