Triple
T20588483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Later Baekje |
E505849
|
entity |
| Predicate | defeatBattle |
P20144
|
FINISHED |
| Object | Battle of Seonsan |
—
|
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 Seonsan | Statement: [Later Baekje, defeatBattle, Battle of Seonsan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Battle of Seonsan Context triple: [Later Baekje, defeatBattle, Battle of Seonsan]
-
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 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.
-
D.
Battle of Hwangsanbeol
The Battle of Hwangsanbeol was a decisive 660 CE clash in the Korean Three Kingdoms period in which Silla forces, allied with Tang China, defeated Baekje and paved the way for Baekje’s collapse.
-
E.
Battle of Soyang River
The Battle of Soyang River was a major engagement of the Korean War in May 1951, in which United Nations forces halted a large-scale Chinese and North Korean offensive in central 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 Seonsan Target entity description: 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.
-
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 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.
-
D.
Battle of Hwangsanbeol
The Battle of Hwangsanbeol was a decisive 660 CE clash in the Korean Three Kingdoms period in which Silla forces, allied with Tang China, defeated Baekje and paved the way for Baekje’s collapse.
-
E.
Battle of Soyang River
The Battle of Soyang River was a major engagement of the Korean War in May 1951, in which United Nations forces halted a large-scale Chinese and North Korean offensive in central 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_69e0b4b9669c8190b8e81fc72817d42c |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a9790cc08190b48949834cd421d2 |
completed | April 20, 2026, 10:32 p.m. |
Created at: April 16, 2026, 11:40 a.m.