Triple
T20322183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geneva Communiqué of 30 June 2012 |
E492232
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international diplomatic agreement |
C2056
|
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: international diplomatic agreement Context triple: [Geneva Communiqué of 30 June 2012, instanceOf, international diplomatic agreement]
-
A.
international agreement
An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
-
B.
international diplomatic document
chosen
An international diplomatic document is a formal written instrument exchanged between states or international organizations to record, communicate, or formalize agreements, positions, or understandings in the conduct of foreign relations.
-
C.
international policy instrument
An international policy instrument is a formal agreement, framework, or mechanism used by multiple countries or international organizations to coordinate actions, set standards, or achieve shared policy objectives across borders.
-
D.
international political decision
An international political decision is a formal choice or policy action made by one or more states or global governing bodies that shapes relations, obligations, or power dynamics across national borders.
-
E.
international political declaration
An international political declaration is a formal, non-binding statement adopted by states or international bodies that articulates shared political intentions, principles, or commitments on global or regional issues.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:20 a.m.