Triple
T19254818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bagelkhand |
E481487
|
entity |
| Predicate | majorCity |
P316
|
FINISHED |
| Object | Singrauli |
—
|
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: Singrauli | Statement: [Bagelkhand, majorCity, Singrauli]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Singrauli Context triple: [Bagelkhand, majorCity, Singrauli]
-
A.
Singrauli
chosen
Singrauli is a major industrial and energy hub in central India, known for its extensive coal mining operations and large thermal power plants.
-
B.
Bhor
Bhor is a small town in Maharashtra, India, known for its scenic surroundings in the Western Ghats and proximity to Pune.
-
C.
Melghat
Melghat is a legislative assembly constituency in Maharashtra, India, known for its predominantly tribal population and forested, hilly terrain.
-
D.
Shivpuri
Shivpuri is a historic town and former princely state in central India, known for its forests, wildlife sanctuaries, and royal palaces.
-
E.
Satpura region
The Satpura region is a hilly, forested plateau area in central India known for its rich biodiversity, tribal communities, and the Satpura Range that runs through states like Madhya Pradesh and Maharashtra.
- 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_69e5fb3459d08190a7c28ed3f8c82a97 |
completed | April 20, 2026, 10:08 a.m. |
Created at: April 10, 2026, 1:28 p.m.