Triple

T20180032
Position Surface form Disambiguated ID Type / Status
Subject Legislative Council of Eastern Bengal and Assam E492702 entity
Predicate instanceOf P0 FINISHED
Object British Indian legislative body C12459 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 legislative body
Context triple: [Legislative Council of Eastern Bengal and Assam, instanceOf, British Indian legislative body]
  • A. British Indian administrative body chosen
    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. 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.
  • C. provincial party in British India
    A provincial party in British India was a regionally based political organization that operated within a specific province, representing local interests and communities under colonial rule and often mediating between nationalist movements and the British administration.
  • D. British colonial federation
    A British colonial federation is a proposed or actual political union that grouped multiple British colonies under a single federal structure to centralize governance while retaining local administrations.
  • E. state assembly of India
    The state assembly of India is a legislative body at the state level responsible for making laws, approving budgets, and overseeing the executive within that state.
  • 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_69da6268a034819081cbd9ea5a1c9475 completed April 11, 2026, 3:02 p.m.
Created at: April 11, 2026, 11:36 p.m.