Triple
T22989494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | inter-Korean summits |
E572006
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | inter-Korean relations event |
C2909
|
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 relations event Context triple: [inter-Korean summits, instanceOf, inter-Korean relations event]
-
A.
Korean Demilitarized Zone incident
A Korean Demilitarized Zone incident is a specific event involving military, political, or security-related confrontation, provocation, or violation occurring in or around the Korean Demilitarized Zone between North and South Korea.
-
B.
United States–Russia relations event
A United States–Russia relations event is a specific occurrence, interaction, or development that significantly affects the political, diplomatic, military, economic, or cultural relationship between the United States and Russia.
-
C.
diplomatic incident
chosen
A diplomatic incident is an event or action involving representatives of different states that causes tension, conflict, or embarrassment in their official relations.
-
D.
Taiwan Strait crisis
The Taiwan Strait crisis refers to recurring periods of heightened military and political tension between the People’s Republic of China, the Republic of China (Taiwan), and often the United States, centered on sovereignty disputes and the risk of armed conflict across the Taiwan Strait.
-
E.
anti-Chinese incident
An anti-Chinese incident is an event or action, ranging from verbal harassment to physical violence or discriminatory policies, specifically targeting individuals, communities, or institutions perceived as Chinese.
- 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_69e245b535808190adef8a9df3c584db |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:49 p.m.