Triple
T1172908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Status of Forces Agreement between U.S. and Iraq (2008) |
E24954
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Status of Forces Agreement |
C824
|
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: Status of Forces Agreement Context triple: [Status of Forces Agreement between U.S. and Iraq (2008), instanceOf, Status of Forces Agreement]
-
A.
collective defense agreement
A collective defense agreement is a formal pact among multiple states committing each to consider an attack on one member as an attack on all and to respond with coordinated defense measures.
-
B.
treaty
A treaty is a formal, legally binding agreement between two or more sovereign states or international entities that defines their mutual rights, obligations, and commitments.
-
C.
international agreement
chosen
An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
-
D.
trilateral security partners
Trilateral security partners are three sovereign entities that formally coordinate defense, intelligence, and strategic policies to enhance their collective security and regional or global stability.
-
E.
NATO military position
A NATO military position is a standardized role or appointment within the North Atlantic Treaty Organization’s integrated command or force structure, defining specific responsibilities, rank equivalencies, and functions across member nations’ armed forces.
- 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_69a494082a7c819095004f423f294a64 |
completed | March 1, 2026, 7:31 p.m. |
Created at: March 1, 2026, 7:45 p.m.