Triple
T33516852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Governor-General of Belgium |
E858388
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial-style administrative title |
C36788
|
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: colonial-style administrative title Context triple: [Governor-General of Belgium, instanceOf, colonial-style administrative title]
-
A.
colonial-style administrative position
A colonial-style administrative position is a formal role within a governance system modeled on historical colonial administrations, typically involving hierarchical authority over territories, resources, and local populations on behalf of a distant central power.
-
B.
instrument of colonial administration
An instrument of colonial administration is any institutional mechanism, policy, or practice deliberately used by a colonial power to govern, control, and extract resources from colonized populations and territories.
-
C.
colonial administrative service
A colonial administrative service is a bureaucratic organization established by a colonial power to govern, manage, and implement policies in its overseas territories.
-
D.
colonial officer
A colonial officer is an official appointed by a colonial power to administer, govern, and enforce its policies and interests within a colonized territory.
-
E.
colonial governor (de jure)
chosen
A colonial governor (de jure) is the legally recognized official appointed or authorized by a sovereign state to exercise formal governing authority over a colony, regardless of their actual ability to enforce that authority in practice.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:39 a.m.