Triple
T11095926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William H. Pitsenbarger |
E262379
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military personnel killed in the Vietnam War |
C21208
|
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: military personnel killed in the Vietnam War Context triple: [William H. Pitsenbarger, instanceOf, military personnel killed in the Vietnam War]
-
A.
event in the Vietnam War
An event in the Vietnam War is a specific, temporally bounded occurrence—such as a battle, operation, political decision, or diplomatic action—that significantly influenced the course, conduct, or consequences of the conflict.
-
B.
military personnel killed in World War II
Individuals who served in the armed forces of any nation and lost their lives as a direct result of military operations or related wartime activities during World War II (1939–1945).
-
C.
person killed in action
chosen
A person killed in action is an individual who dies while actively engaged in a military or combat operation.
-
D.
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.
-
E.
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.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:27 p.m.