Triple
T22092053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bengal famine of 1770 |
E545935
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | disaster in British India |
C45786
|
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: disaster in British India Context triple: [Bengal famine of 1770, instanceOf, disaster in British India]
-
A.
Indian empire
The Indian empire is a vast, historically rich civilization-state encompassing diverse cultures, religions, and political entities that have risen and fallen across the Indian subcontinent over millennia.
-
B.
division of British India
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.
-
C.
presidency of British India
The presidency of British India was a major administrative division governed by the British East India Company and later the British Crown, serving as a regional center of political, military, and economic control.
-
D.
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.
-
E.
Anglo-Afghan War
The Anglo-Afghan War refers to any of three 19th- and early 20th-century conflicts between the British Empire and Afghanistan, fought primarily over imperial influence and control in Central Asia.
- F. None of above. chosen
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_69e11e36d03c8190a83a1ba802b7231b |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:29 p.m.