Triple

T13888331
Position Surface form Disambiguated ID Type / Status
Subject Judicial and Public Department E333905 entity
Predicate instanceOf P0 FINISHED
Object division of the India Office 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 the India Office
Context triple: [Judicial and Public Department, instanceOf, division of the India Office]
  • A. division of British India chosen
    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.
  • B. 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.
  • 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. colonial office
    A colonial office is a governmental department or administrative body responsible for managing and overseeing the affairs, policies, and governance of a colony or group of colonies on behalf of a colonial power.
  • E. 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.
  • 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_69d81c5dd2d48190b7a5fc1e009de936 completed April 9, 2026, 9:38 p.m.
Created at: April 9, 2026, 10:15 p.m.