Triple
T21142783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gujarat princely states |
E520974
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former subdivision of British India |
C34305
|
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: former subdivision of British India Context triple: [Gujarat princely states, instanceOf, former subdivision 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 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.
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.
-
D.
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.
-
E.
former subdivision of a country
chosen
A former subdivision of a country is an administrative region or territorial unit that once existed within a nation’s political structure but has since been reorganized, merged, renamed, or abolished.
- 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:57 p.m.