Triple
T16948891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korean War U.S. Army infantry veterans |
E411134
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Korean War veterans |
C6728
|
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 War veterans Context triple: [Korean War U.S. Army infantry veterans, instanceOf, Korean War veterans]
-
A.
World War II veteran
A World War II veteran is an individual who served in the armed forces of any nation during the global conflict of 1939–1945, participating in military operations or support roles related to the war.
-
B.
Japanese military personnel of World War II
Individuals who served in the armed forces of the Empire of Japan during World War II, including the Imperial Japanese Army, Navy, and associated military organizations.
-
C.
military veteran
chosen
A military veteran is an individual who has previously served in a nation's armed forces and has since been discharged or retired from active duty.
-
D.
engagement of the Korean War
The engagement of the Korean War is a military operation or battle episode involving armed forces of opposing sides during the 1950–1953 conflict on the Korean Peninsula, characterized by direct combat, maneuver, and tactical interaction within a defined time and area.
-
E.
Polish–Ukrainian War veteran
A Polish–Ukrainian War veteran is an individual who served as a combatant or military participant in the conflict between Poland and the West Ukrainian People's Republic from 1918 to 1919.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:31 a.m.