Triple
T32792804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kim Yu-sin |
E838676
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Korean general |
C59703
|
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 general Context triple: [Kim Yu-sin, instanceOf, Korean general]
-
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.
South Vietnamese general
A South Vietnamese general is a high-ranking military officer who served in the armed forces of the Republic of Vietnam (1955–1975), typically responsible for commanding major units, shaping military strategy, and often playing a significant role in the country’s political affairs during the Vietnam War.
-
C.
Joseon Dynasty military officer
A Joseon Dynasty military officer was a state-appointed commander responsible for organizing, training, and leading troops in defense of the Korean kingdom, enforcing royal authority, and maintaining regional security according to Confucian-based military hierarchies.
-
D.
Burmese general
A Burmese general is a high-ranking military officer in Myanmar’s armed forces, typically wielding significant political influence and authority over national security and governance.
-
E.
Chu general
A Chu general is a high-ranking military commander from the ancient Chinese state of Chu, responsible for leading armies, planning campaigns, and defending or expanding the state's territories.
- F. None of above. chosen
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_69f3493c7f6881908edf2aa13631d1e0 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:14 a.m.