Triple
T14031096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colonial Secretary of Tasmania |
E337588
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial public office |
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 public office Context triple: [Colonial Secretary of Tasmania, instanceOf, colonial public office]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:20 p.m.