Triple
T20129971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sehore Municipal Council |
E490862
|
entity |
| Predicate | governs |
P760
|
FINISHED |
| Object | Sehore town |
—
|
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: Sehore town | Statement: [Sehore Municipal Council, governs, Sehore town]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sehore town Context triple: [Sehore Municipal Council, governs, Sehore town]
-
A.
Sohna town
Sohna town is a rapidly developing suburban area in Haryana, India, known for its hot springs, proximity to the Aravalli hills, and growing residential and commercial hubs.
-
B.
Sehore
chosen
Sehore is a town and district headquarters in central India, located near the state capital Bhopal in Madhya Pradesh.
-
C.
Sehore district
Sehore district is an administrative region in the central Indian state of Madhya Pradesh, known for its agricultural landscape and network of rivers and streams.
-
D.
Taranagar
Taranagar is a town in the Churu district of Rajasthan, India, known for its regional trade, educational institutions, and cultural heritage.
-
E.
Laharpur
Laharpur is a town and municipal body in the Sitapur district of Uttar Pradesh, India.
- 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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e66760b8f08190a66fbb2e9e3925a3 |
completed | April 20, 2026, 5:50 p.m. |
Created at: April 11, 2026, 11:31 p.m.