Triple

T19324967
Position Surface form Disambiguated ID Type / Status
Subject Pacific Mandate territories E483323 entity
Predicate instanceOf P0 FINISHED
Object League of Nations mandate territory C2332 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: League of Nations mandate territory
Context triple: [Pacific Mandate territories, instanceOf, League of Nations mandate territory]
  • A. League of Nations mandate chosen
    A League of Nations mandate was a legal and administrative arrangement by which a victorious World War I power governed a former German or Ottoman territory under international supervision, ostensibly until it was deemed ready for self-rule.
  • B. United Nations trust territory
    A United Nations trust territory is a non-self-governing territory placed under the administration of a member state by the UN Trusteeship Council, with the goal of promoting its advancement toward self-government or independence.
  • C. former German colony
    A former German colony is a territory that was once under the political control and administration of the German Empire or later German states, but has since gained independence or come under another sovereignty.
  • D. bivša međunarodna teritorija
    Bivša međunarodna teritorija je geografsko područje koje je u prošlosti bilo pod međunarodnom upravom ili nadzorom više država ili međunarodne organizacije, ali je kasnije dobilo drugačiji političko-pravni status.
  • E. non-self-governing territory
    A non-self-governing territory is a geographic area under the administrative control of another state where the local population has not yet achieved full self-government or independence.
  • 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_69d8e8d13e3c81909d91d1d5ec37c095 completed April 10, 2026, 12:10 p.m.
Created at: April 10, 2026, 1:32 p.m.