Triple

T22459844
Position Surface form Disambiguated ID Type / Status
Subject British Java E555200 entity
Predicate instanceOf P0 FINISHED
Object British colonial rule C46210 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 rule
Context triple: [British Java, instanceOf, British colonial rule]
  • A. British colonial position
    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.
  • B. British colonial residency
    A British colonial residency was an official administrative and diplomatic establishment where a British Resident lived and worked to oversee, advise, and often indirectly control the affairs of a princely state or protectorate within the British Empire.
  • C. government of a British colony chosen
    The government of a British colony is the administrative and political authority established by the British Crown to rule and manage a colonial territory, typically headed by a governor and supported by appointed and sometimes elected councils.
  • 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. period of English overseas rule
    A period of English overseas rule is a historical era during which England established and governed territories beyond its own borders, exerting political, economic, and cultural control over distant lands.
  • 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_69e11e51fdec8190adfdf9f8a6362221 completed April 16, 2026, 5:37 p.m.
Created at: April 16, 2026, 8:48 p.m.