Triple
T22382918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia colonial government |
E553319
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government of a British colony |
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: government of a British colony Context triple: [Virginia colonial government, instanceOf, government of a British colony]
-
A.
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.
-
B.
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.
-
C.
British penal colony
A British penal colony is a distant settlement established by the British government primarily to confine, punish, and exploit the labor of transported convicts.
-
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.
former colonial settlement
A former colonial settlement is a community or territory originally established and governed by a foreign colonial power that has since transitioned to local or independent control, often retaining cultural, architectural, and institutional legacies of its colonial past.
- F. None of above. chosen
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_69e11e4cf87c8190a1ff474daec326b7 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:45 p.m.