Triple
T5432668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Battle of Yeonpyeong |
E121532
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | inter-Korean conflict |
C8411
|
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 conflict Context triple: [Second Battle of Yeonpyeong, instanceOf, inter-Korean conflict]
-
A.
border conflict
chosen
A border conflict is a dispute between neighboring states or groups over the ownership, control, or demarcation of a shared territorial boundary.
-
B.
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.
-
C.
geopolitical conflict
A geopolitical conflict is a sustained struggle between nations or political entities driven by competing interests over territory, resources, ideology, or influence on the global stage.
-
D.
military confrontation
A military confrontation is an armed clash between organized state or non-state forces, involving the use or threat of force to achieve political, territorial, or strategic objectives.
-
E.
civil conflict
Civil conflict is a sustained, organized struggle within a country between the state and one or more internal groups, or among such groups themselves, involving political, social, or economic grievances and often resulting in violence.
- 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_69bd463c65f0819082ee6483ab4b466a |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:06 p.m.