Triple

T6311800
Position Surface form Disambiguated ID Type / Status
Subject Government-General of Korea E141520 entity
Predicate instanceOf P0 FINISHED
Object Japanese colonial administration C20309 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: Japanese colonial administration
Context triple: [Government-General of Korea, instanceOf, Japanese colonial administration]
  • A. Japanese colonial administrator
    A Japanese colonial administrator is an official appointed by the Japanese government to govern, manage, and implement imperial policies in occupied or colonized territories.
  • B. Japanese imperial office
    A Japanese imperial office is a governmental or court position within the historical or modern Japanese imperial system, responsible for specific administrative, ceremonial, or advisory functions under the authority of the Emperor.
  • C. Japanese military administration unit
    A Japanese military administration unit is an organizational entity within Japan’s armed forces responsible for managing logistics, personnel, planning, and support functions necessary to sustain military operations.
  • D. Bugis polity
    A Bugis polity is a traditional socio-political entity of the Bugis people of South Sulawesi, typically organized around a kingdom or chiefdom with its own ruler, customary laws, and maritime-oriented economy and alliances.
  • E. Japanese imperial law
    Japanese imperial law is the body of legal principles, statutes, and institutional practices that governed the authority, succession, and functions of the Emperor and imperial household within Japan’s historical and constitutional frameworks.
  • F. None of above. chosen

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_69c008d00efc8190a36c05b4b4a3bf4b completed March 22, 2026, 3:20 p.m.
Created at: March 22, 2026, 4:28 p.m.