Triple
T5998340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bengal Presidency |
E133529
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative division of British India |
C13599
|
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: administrative division of British India Context triple: [Bengal Presidency, instanceOf, administrative division of British India]
-
A.
district of British India
chosen
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.
administrative district of India
An administrative district of India is a territorial subdivision of a state or union territory, governed by district-level authorities to manage local administration, law and order, and development activities.
-
C.
subdivision of a district in India
A subdivision of a district in India is an administrative unit below the district level that groups several tehsils or blocks to facilitate local governance, revenue administration, and public service delivery.
-
D.
former division of Pakistan
A former division of Pakistan is an obsolete administrative unit that once functioned as an intermediate tier of government between the provincial and district levels before being abolished or reorganized.
-
E.
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.
- 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_69c00870ddbc81909880fa3864f4f38d |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:05 p.m.