Triple
T30610252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Commission Territories in Southern Africa |
E779159
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | group of British protectorates |
C11907
|
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: group of British protectorates Context triple: [High Commission Territories in Southern Africa, instanceOf, group of British protectorates]
-
A.
British protectorate
chosen
A British protectorate was a territory that retained its own internal government but was under the protection and partial control of the British Empire, particularly in matters of foreign policy and defense.
-
B.
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.
-
C.
former British colony
A former British colony is a territory that was once governed or administered by the British Empire but has since gained independence or undergone a change in political status.
-
D.
group of princely states
A group of princely states is a collection of semi-autonomous, monarch-ruled territories historically bound together under a larger imperial or colonial framework for purposes of governance, diplomacy, or administration.
-
E.
United Nations trust territory
A United Nations trust territory is a non-self-governing territory placed under the administration of a member state by the UN Trusteeship Council, with the goal of promoting its advancement toward self-government or independence.
- 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_69f224a21fc08190abd9d8dd9eb6bb4c |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:26 p.m.