Triple
T3505720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of the Governor-General |
E74070
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial governing council |
C308
|
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 governing council Context triple: [Council of the Governor-General, instanceOf, colonial governing council]
-
A.
colonial government
A colonial government is the political and administrative system imposed by a foreign power to control and manage a colony’s territory, resources, and population, typically subordinating local authority to the interests of the colonizing state.
-
B.
governing council
chosen
A governing council is a formal body of appointed or elected individuals responsible for making high-level decisions, setting policies, and providing oversight for an organization, community, or institution.
-
C.
colonial legislature
A colonial legislature is a representative governing body established in a colony to create laws, manage local affairs, and advise or balance the authority of the colonial governor and imperial power.
-
D.
colonial office
A colonial office is a governmental department or administrative body responsible for managing and overseeing the affairs, policies, and governance of a colony or group of colonies on behalf of a colonial power.
-
E.
colonial political organization
A colonial political organization is a governing structure imposed by a foreign power to administer, control, and exploit a colonized territory and its population, often subordinating local institutions and interests to imperial objectives.
- 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:18 p.m.