Triple
T20801118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington Declaration 2012 |
E512041
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bilateral security document |
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: bilateral security document Context triple: [Washington Declaration 2012, instanceOf, bilateral security document]
-
A.
bilateral military agreement
A bilateral military agreement is a formal pact between two states that outlines mutual defense commitments, security cooperation, and related military obligations and activities.
-
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.
bilateral commission
A bilateral commission is a formal joint body established by two parties, typically states or organizations, to negotiate, coordinate, and oversee matters of mutual interest.
-
D.
bilateral meeting
A bilateral meeting is a formal or informal discussion between representatives of two distinct parties, typically organizations or countries, to negotiate, coordinate, or resolve specific issues of mutual interest.
-
E.
state security archives
State security archives are institutional collections of records, documents, and surveillance materials produced or gathered by state security and intelligence agencies in the course of monitoring, controlling, and protecting a nation’s political and social order.
- 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_69e0b4cc69f481908e98751e697b9df4 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:39 p.m.