Triple
T36711807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Security of Military Information Agreement (GSOMIA) |
E906812
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bilateral security agreement |
C44101
|
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 agreement Context triple: [General Security of Military Information Agreement (GSOMIA), instanceOf, bilateral security agreement]
-
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.
bilateral diplomatic agreement
chosen
A bilateral diplomatic agreement is a formal, negotiated arrangement between two sovereign states that defines mutual rights, obligations, and cooperative actions in specific areas of shared interest.
-
C.
bilateral economic agreement
A bilateral economic agreement is a formal arrangement between two countries that establishes rules and commitments to govern their economic relations, such as trade, investment, and financial cooperation.
-
D.
bilateral relations
Bilateral relations are the political, economic, and diplomatic interactions and agreements that occur directly between two sovereign states.
-
E.
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.
- 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_69f76e73ad108190a5241585f2303e9a |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.