Triple
T19867101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Normandy Format |
E477418
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | diplomatic negotiation framework |
C2127
|
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 negotiation framework Context triple: [Normandy Format, instanceOf, diplomatic negotiation framework]
-
A.
multilateral negotiation process
chosen
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.
-
B.
diplomatic conference
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 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.
-
D.
diplomatic convention
A diplomatic convention is a formal international agreement or treaty that establishes rules, procedures, or standards governing relations and conduct between states.
-
E.
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.
- 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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:51 p.m.