Triple
T9539561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryti–Ribbentrop Agreement |
E230113
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | diplomatic pledge |
C2901
|
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: diplomatic pledge Context triple: [Ryti–Ribbentrop Agreement, instanceOf, diplomatic pledge]
-
A.
ceremonial pledge
A ceremonial pledge is a formal, often ritualized promise or vow publicly declared to affirm commitment to a person, group, principle, or cause.
-
B.
diplomatic declaration
chosen
A diplomatic declaration is a formal, often public statement issued by a state or group of states to articulate positions, intentions, or commitments in international relations.
-
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.
diplomatic initiative
A diplomatic initiative is a coordinated effort by one or more states or international actors to open, advance, or resolve political, economic, or security issues through negotiation and dialogue rather than coercion or conflict.
-
E.
legal pledge
A legal pledge is a formal commitment, often documented and enforceable by law, in which a party promises to fulfill specific obligations or refrain from certain actions, typically as security or assurance in a legal or contractual context.
- 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.