Triple
T19975610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malwa Agency |
E493682
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British Indian administrative subdivision |
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: British Indian administrative subdivision Context triple: [Malwa Agency, instanceOf, British Indian administrative subdivision]
-
A.
British Indian administrative body
A British Indian administrative body is a colonial-era governing institution established by the British in India to manage political, legal, and economic affairs on behalf of the imperial government.
-
B.
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.
-
C.
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.
-
D.
British colonial administrative body
A British colonial administrative body is an official governing institution established by the British Empire to manage political, economic, and legal affairs in its overseas territories.
-
E.
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.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 3:25 p.m.