Triple

T8872127
Position Surface form Disambiguated ID Type / Status
Subject William Keeling E211182 entity
Predicate instanceOf P0 FINISHED
Object East India Company officer C21445 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: East India Company officer
Context triple: [William Keeling, instanceOf, East India Company officer]
  • A. British East India Company officer chosen
    A British East India Company officer was a commissioned military or administrative official serving under the Company’s authority in India and other colonial territories, responsible for enforcing its policies, protecting its commercial interests, and often exercising significant political and military power.
  • B. British East India Company regiment
    A British East India Company regiment was a military unit raised, organized, and maintained by the Company in India to protect its commercial interests, enforce territorial control, and support colonial governance.
  • C. organ of the British East India Company
    An organ of the British East India Company is any official body, office, or instrument through which the Company exercised its administrative, commercial, or political functions.
  • D. British colonial administrator
    A British colonial administrator is an official appointed by the British government to govern, manage, and implement imperial policies in overseas colonies, overseeing local administration, law, and economic exploitation.
  • E. Mughal official
    A Mughal official was an appointed administrator or noble in the Mughal Empire responsible for governing territories, collecting revenue, maintaining law and order, and implementing imperial policies on behalf of the emperor.
  • 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_69ca838e78748190934d82db3104f855 completed March 30, 2026, 2:07 p.m.
Created at: March 30, 2026, 6:51 p.m.