Triple
T1423872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Conference of 1926 |
E30284
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Imperial Conference |
C69
|
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: Imperial Conference Context triple: [Imperial Conference of 1926, instanceOf, Imperial Conference]
-
A.
World War II conference
A World War II conference is a high-level diplomatic meeting held among Allied or Axis leaders during the war to coordinate military strategy, negotiate political arrangements, and shape postwar plans.
-
B.
diplomatic conference
chosen
A diplomatic conference is a formal gathering of representatives from different states or international organizations convened to negotiate agreements, resolve disputes, or discuss issues of mutual concern.
-
C.
League of Nations mandate
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.
-
D.
British imperial inquiry
A British imperial inquiry is a formal investigation commissioned by the British Empire or its government to examine events, policies, or conditions in colonial territories, often to manage crises, legitimize authority, or recommend administrative reforms.
-
E.
imperial confederation
An imperial confederation is a loose union of semi-autonomous states or territories under the overarching authority of an empire, which coordinates common policies while allowing substantial local self-rule.
- 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_69a498fb823c8190a67ce4c4837e641a |
completed | March 1, 2026, 7:52 p.m. |
Created at: March 1, 2026, 8 p.m.