Triple
T501914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Munich Agreement |
E10419
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | appeasement policy milestone |
C2969
|
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: appeasement policy milestone Context triple: [Munich Agreement, instanceOf, appeasement policy milestone]
-
A.
Cold War policy
Cold War policy refers to the strategic, political, military, and economic decisions and doctrines adopted by states—primarily the United States and the Soviet Union—to contain, compete with, or influence each other and their allies without escalating into direct large-scale war.
-
B.
political agreement
A political agreement is a negotiated understanding or formal accord between political actors or entities that defines shared commitments, terms, and responsibilities on specific issues or policies.
-
C.
diplomatic position
A diplomatic position is an official role within a government or international organization responsible for managing and representing a state's or entity's interests in foreign relations and negotiations.
-
D.
Cold War polity
A Cold War polity is a state or political entity whose institutions, policies, and international behavior are fundamentally shaped by the ideological, military, and geopolitical tensions between the U.S.-led Western bloc and the Soviet-led Eastern bloc from roughly 1947 to 1991.
-
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. 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_69a2e848adf881908e5e04f7af030093 |
completed | Feb. 28, 2026, 1:06 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.