Triple
T20790810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Seong of Baekje |
E511769
|
entity |
| Predicate | diedIn |
P21
|
FINISHED |
| Object | Battle of Gwansan Fortress |
—
|
NE NERFINISHED |
How this triple was built (3 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Battle of Gwansan Fortress | Statement: [King Seong of Baekje, diedIn, Battle of Gwansan Fortress]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Battle of Gwansan Fortress Context triple: [King Seong of Baekje, diedIn, Battle of Gwansan Fortress]
-
A.
Battle of Seonghwan
The Battle of Seonghwan was an early land engagement in 1894 during the First Sino-Japanese War in which Japanese forces defeated Chinese troops near Asan in Korea, helping secure Japanese control over the Korean Peninsula.
-
B.
Battle of Baengma-goji
The Battle of Baengma-goji, also known as the Battle of White Horse, was a fierce and pivotal Korean War engagement in 1952 in which United Nations forces, primarily South Korean troops, repeatedly repelled Chinese assaults to hold a strategically vital hill.
-
C.
Battle of Gochang
The Battle of Gochang was a key military engagement during Korea’s Later Three Kingdoms period in which the kingdom of Later Baekje suffered a significant defeat.
-
D.
Battle of Seonsan
The Battle of Seonsan was a key 10th-century conflict on the Korean peninsula during the Later Three Kingdoms period, marking a significant military setback for the kingdom of Later Baekje.
-
E.
Battle of Wonju
The Battle of Wonju was a key engagement of the Korean War in early 1951, where United Nations forces halted Chinese and North Korean advances in central South Korea.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Battle of Gwansan Fortress Target entity description: The Battle of Gwansan Fortress was a 6th-century conflict between the Korean kingdoms of Baekje and Silla that resulted in a decisive Silla victory and the death of Baekje’s King Seong.
-
A.
Battle of Seonghwan
The Battle of Seonghwan was an early land engagement in 1894 during the First Sino-Japanese War in which Japanese forces defeated Chinese troops near Asan in Korea, helping secure Japanese control over the Korean Peninsula.
-
B.
Battle of Baengma-goji
The Battle of Baengma-goji, also known as the Battle of White Horse, was a fierce and pivotal Korean War engagement in 1952 in which United Nations forces, primarily South Korean troops, repeatedly repelled Chinese assaults to hold a strategically vital hill.
-
C.
Battle of Gochang
The Battle of Gochang was a key military engagement during Korea’s Later Three Kingdoms period in which the kingdom of Later Baekje suffered a significant defeat.
-
D.
Battle of Seonsan
The Battle of Seonsan was a key 10th-century conflict on the Korean peninsula during the Later Three Kingdoms period, marking a significant military setback for the kingdom of Later Baekje.
-
E.
Battle of Wonju
The Battle of Wonju was a key engagement of the Korean War in early 1951, where United Nations forces halted Chinese and North Korean advances in central South Korea.
- F. None of above. chosen
Provenance (2 batches)
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_69e0b4cb83948190bd57bec21d78ed53 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c29010508190bf2cf577d7f64754 |
completed | April 21, 2026, 12:19 a.m. |
Created at: April 16, 2026, 12:38 p.m.