Triple
T7365037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allahabad Division |
E169849
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | division of 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: division of British India Context triple: [Allahabad Division, instanceOf, division of 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 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.
-
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.
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.
-
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. 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_69c68a5ade988190885b7175f63b7534 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:06 p.m.