Triple
T21044488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yi Seong-gye |
E518413
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Korean military leader |
C22817
|
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: Korean military leader Context triple: [Yi Seong-gye, instanceOf, Korean military leader]
-
A.
South Korean Army general
A South Korean Army general is a high-ranking military officer in the Republic of Korea Army responsible for strategic planning, operational command, and leadership of large military formations.
-
B.
Vietnamese military leader
A Vietnamese military leader is a high-ranking commander responsible for planning, directing, and overseeing Vietnam’s armed forces in defense, strategic operations, and national security.
-
C.
Nationalist Chinese military leader
A Nationalist Chinese military leader is a high-ranking officer or commander who served under the Republic of China’s Nationalist government, directing armed forces in defense of its political authority and territorial claims, often in opposition to Communist forces and foreign invaders.
-
D.
Governor-General of Korea
The Governor-General of Korea was the highest-ranking Japanese colonial official who exercised supreme civil, military, and administrative authority over Korea from 1910 to 1945.
-
E.
Military leader
chosen
A military leader is an individual who plans, directs, and coordinates armed forces operations, making strategic and tactical decisions to achieve military objectives while managing and motivating personnel under their command.
- 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_69e0b50438e08190917e2538bb8bc034 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:24 p.m.