Triple
T9539560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryti–Ribbentrop Agreement |
E230113
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | wartime political agreement |
C16010
|
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: wartime political agreement Context triple: [Ryti–Ribbentrop Agreement, instanceOf, wartime political agreement]
-
A.
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.
-
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.
non‑aggression pact
chosen
A non-aggression pact is a formal agreement between two or more parties in which they commit not to engage in military or hostile actions against each other, typically for a specified period.
-
D.
wartime settlement
A wartime settlement is an agreement or arrangement reached during or immediately after armed conflict that defines the terms for ending hostilities, addressing territorial or political disputes, and establishing conditions for postwar order.
-
E.
political-military alliance
A political-military alliance is a formal agreement between two or more states to coordinate their defense and foreign policies, often including mutual security guarantees and joint military planning.
- 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_69ca847b1b3081908f72bc932c17cc41 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:01 p.m.