Triple
T37244542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 樺太庁 |
E923811
|
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 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.
-
B.
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.
-
C.
government of a British colony
The government of a British colony is the administrative and political authority established by the British Crown to rule and manage a colonial territory, typically headed by a governor and supported by appointed and sometimes elected councils.
-
D.
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.
-
E.
frontier government
A frontier government is a provisional or early-stage governing authority established in newly settled or sparsely populated border regions to maintain order, manage resources, and extend the reach of a central state.
- 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_69f76ea9fee88190a589f661d95a7189 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:15 p.m.