Triple
T19701979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | September 19 Military Agreement |
E473119
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | inter-Korean military 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: inter-Korean military agreement Context triple: [September 19 Military Agreement, instanceOf, inter-Korean military agreement]
-
A.
military base agreement
A military base agreement is a formal arrangement between a host nation and a foreign state that defines the rights, responsibilities, and conditions under which the foreign state may establish, operate, and maintain military facilities on the host nation’s territory.
-
B.
non‑aggression pact
A non-aggression pact is a formal agreement between two or more parties in which they commit not to engage in military or hostile actions against each other, typically for a specified period.
-
C.
arms deal
An arms deal is a transaction involving the sale, transfer, or exchange of weapons and military equipment between parties, often states, organizations, or private entities.
-
D.
division of the Korean People's Army
A division of the Korean People's Army is a large, combined-arms military formation typically composed of several regiments and support units, organized to conduct sustained ground combat operations under the command of the KPA.
-
E.
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.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:46 p.m.