Triple
T13888259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Political and Secret Department |
E333903
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial administration body |
C1298
|
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 administration body Context triple: [Political and Secret Department, instanceOf, colonial administration body]
-
A.
British colonial administrative body
A British colonial administrative body is an official governing institution established by the British Empire to manage political, economic, and legal affairs in its overseas territories.
-
B.
public administration body
A public administration body is an organization within the public sector responsible for implementing laws, delivering public services, and managing governmental policies and resources on behalf of the state and its citizens.
-
C.
colonial office
chosen
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.
-
D.
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.
-
E.
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.
- 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:15 p.m.