Triple

T7155794
Position Surface form Disambiguated ID Type / Status
Subject South Seas Mandate E166808 entity
Predicate instanceOf P0 FINISHED
Object Japanese colonial territory C5628 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 territory
Context triple: [South Seas Mandate, instanceOf, Japanese colonial territory]
  • A. colonial territory chosen
    A colonial territory is a geographic area under the political control and administration of a distant foreign power, typically exploited for economic, strategic, or settlement purposes.
  • B. 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.
  • C. Dutch colonial territory
    A Dutch colonial territory is a region outside Europe that was politically and economically controlled and administered by the Netherlands as part of its overseas empire.
  • D. former Dutch colony
    A former Dutch colony is a territory that was once governed, administered, or significantly controlled by the Netherlands as part of its overseas colonial empire, but has since gained independence or been transferred to another sovereignty.
  • E. former dependent territory
    A former dependent territory is a geographic area that was once politically, economically, or administratively controlled by another sovereign state but has since gained independence or a different political status.
  • 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_69c68887a5cc8190bec0ea96227164f7 completed March 27, 2026, 1:39 p.m.
Created at: March 27, 2026, 2:47 p.m.