Triple
T31178698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berar Province |
E794829
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | territory under British India |
C22080
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: territory under British India Context triple: [Berar Province, instanceOf, territory under British India]
-
A.
district of British India
A district of British India was an administrative subdivision governed by colonial authorities, typically comprising multiple towns and villages, used for managing revenue collection, law and order, and local governance under the British Raj.
-
B.
former state of India
A former state of India is a political and administrative unit that once existed within the Republic of India but was later dissolved, merged, renamed, or reorganized into one or more different states or union territories.
-
C.
division of British India
chosen
A division of British India was an administrative subdivision of a province, grouping several districts under a divisional commissioner for more efficient colonial governance and control.
-
D.
region of India
A region of India is a geographically and culturally distinct area within the country, often defined by shared historical, linguistic, economic, or administrative characteristics.
-
E.
Jat-ruled state
A Jat-ruled state is a political entity or kingdom historically governed by rulers from the Jat community, typically characterized by agrarian-based power structures and regional autonomy in North India.
- F. None of above.
Provenance (1 batch)
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_69f224d675d08190957198068e440422 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:08 p.m.