Triple
T21685265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 朝鮮総督府 |
E535213
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 植民地統治機関 |
C4090
|
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: 植民地統治機関 Context triple: [朝鮮総督府, instanceOf, 植民地統治機関]
-
A.
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.
-
B.
colonial government
chosen
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.
-
C.
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.
-
D.
colonial institutions
Colonial institutions are the formal and informal political, legal, economic, and social structures established by colonial powers to govern, extract resources from, and control colonized populations, often leaving long-lasting impacts on postcolonial societies.
-
E.
Japanese colonial administration
Japanese colonial administration refers to the governmental, military, and bureaucratic systems established by the Empire of Japan to control, exploit, and assimilate its overseas territories from the late 19th century through World War II.
- 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:44 p.m.