Triple
T771188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | remilitarization of the Rhineland |
E16284
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | diplomatic crisis |
C2909
|
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 crisis Context triple: [remilitarization of the Rhineland, instanceOf, diplomatic crisis]
-
A.
diplomatic incident
chosen
A diplomatic incident is an event or action involving representatives of different states that causes tension, conflict, or embarrassment in their official relations.
-
B.
nuclear weapons crisis
A nuclear weapons crisis is a high-stakes international confrontation in which the use or threatened use of nuclear arms becomes a realistic possibility, creating urgent risks of catastrophic escalation and intense diplomatic, military, and political pressure to resolve the conflict.
-
C.
crisis
A crisis is a critical turning point or period of intense difficulty and instability that demands urgent decision-making and action to prevent severe negative consequences.
-
D.
diplomatic relations
Diplomatic relations are the formal and informal interactions and agreements between sovereign states or international actors aimed at managing conflicts, fostering cooperation, and advancing mutual interests through negotiation and representation.
-
E.
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.
- 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_69a49369a0848190af883934cee3db4c |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:37 p.m.