Triple
T10663112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish–German negotiations of the 1930s |
E251277
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | diplomatic negotiations |
C69
|
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 negotiations Context triple: [Polish–German negotiations of the 1930s, instanceOf, diplomatic negotiations]
-
A.
diplomatic policy
Diplomatic policy is a strategic framework guiding a state’s interactions and negotiations with other international actors to advance its political, economic, and security interests while managing conflicts and alliances.
-
B.
diplomatic conference
chosen
A diplomatic conference is a formal gathering of representatives from different states or international organizations convened to negotiate agreements, resolve disputes, or discuss issues of mutual concern.
-
C.
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.
-
D.
multilateral negotiation process
A multilateral negotiation process is a structured series of interactions among three or more parties with differing interests, aimed at reaching mutually acceptable agreements through communication, bargaining, and compromise.
-
E.
diplomatic issue
A diplomatic issue is a matter of contention or concern between states or international actors that requires negotiation, communication, or policy decisions to manage or resolve.
- 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:08 p.m.