Triple

T5217063
Position Surface form Disambiguated ID Type / Status
Subject High Commissioner for Egypt E117778 entity
Predicate instanceOf P0 FINISHED
Object British colonial administrator position C10373 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 colonial administrator position
Context triple: [High Commissioner for Egypt, instanceOf, British colonial administrator position]
  • A. 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.
  • B. British civil service position
    A British civil service position is a professional role within the UK government’s permanent administrative machinery, responsible for implementing policies, delivering public services, and supporting ministers in their official duties.
  • C. British civil servant
    A British civil servant is a non-political government employee who supports the administration and implementation of public policy within the United Kingdom’s civil service.
  • D. British colonial position chosen
    A British colonial position is an official role or office established by the British Empire to administer, govern, or oversee territories and populations under colonial rule.
  • 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_69bd4464ba3c8190bc16b2ebbe42ddb0 completed March 20, 2026, 12:58 p.m.
Created at: March 20, 2026, 1:48 p.m.