Triple
T20441887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Madhya Pradesh |
E501414
|
entity |
| Predicate | majorCity |
P316
|
FINISHED |
| Object | Sheopur |
—
|
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: Sheopur | Statement: [Northern Madhya Pradesh, majorCity, Sheopur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sheopur Context triple: [Northern Madhya Pradesh, majorCity, Sheopur]
-
A.
Sheopur
chosen
Sheopur is a town and district headquarters in the northern part of the Indian state of Madhya Pradesh, known for its proximity to the Kuno National Park and its largely rural, agrarian surroundings.
-
B.
Ishwarpur
Ishwarpur is a municipality-level city located in Nepal’s Madhesh Province.
-
C.
Sahaspur
Sahaspur is a legislative assembly constituency located in the Dehradun district of the Indian state of Uttarakhand.
-
D.
Shankarpur
Shankarpur is a quiet seaside village and emerging beach destination on the Bay of Bengal in West Bengal, India, known for its fishing harbor and relatively uncrowded shoreline.
-
E.
Daryapur
Daryapur is a town in the Amravati district of Maharashtra, India, known for its agricultural economy and regional market activities.
- 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_69e0b4ab3cfc8190ac9bf32e932316b1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e685f3b794819080745b135a305ba7 |
completed | April 20, 2026, 8 p.m. |
Created at: April 16, 2026, 11:32 a.m.