Triple
T4477448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Status of Forces Agreement between the United States and South Korea |
E100043
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | status of forces agreement |
C566
|
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 the United States and South Korea, 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.
co-belligerent state
A co-belligerent state is a country that fights alongside another state against a common enemy in an armed conflict without necessarily being formally allied or bound by a mutual defense treaty.
-
C.
treaty
chosen
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.
-
D.
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.
-
E.
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.
- 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_69b34553cbe48190afa8ac1cac285b86 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:35 p.m.