Triple
T19372547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglo-Soviet Treaty of 1942 |
E484578
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II treaty |
C41100
|
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: World War II treaty Context triple: [Anglo-Soviet Treaty of 1942, instanceOf, World War II treaty]
-
A.
World War II-era treaty
chosen
A World War II-era treaty is a formal, legally binding agreement between nations made during or immediately surrounding the Second World War, typically addressing military alliances, territorial changes, peace terms, or postwar political and economic arrangements.
-
B.
World War I–era diplomatic agreement
A World War I–era diplomatic agreement is a formal treaty, pact, or understanding negotiated between states during or immediately surrounding the First World War, aimed at managing alliances, territorial claims, military commitments, or postwar settlements.
-
C.
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.
-
D.
Cold War–era treaty
A Cold War–era treaty is a formal international agreement, typically between rival blocs or superpowers, designed to manage ideological conflict, arms competition, and spheres of influence during the mid-20th-century geopolitical standoff.
-
E.
treaty
A treaty is a formal, legally binding agreement between two or more sovereign states or international entities that defines their mutual rights, obligations, and commitments.
- 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:35 p.m.