Triple
T16948890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korean War U.S. Army infantry veterans |
E411134
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Army personnel |
C7744
|
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: United States Army personnel Context triple: [Korean War U.S. Army infantry veterans, instanceOf, United States Army personnel]
-
A.
American military personnel
chosen
American military personnel are individuals who serve in the United States Armed Forces, including the Army, Navy, Air Force, Marine Corps, Space Force, and Coast Guard, in roles ranging from combat and support to technical and administrative duties.
-
B.
United States Army position
A United States Army position is a specific role or job within the Army’s organizational structure, defined by rank, responsibilities, and duties in support of military operations and administration.
-
C.
military personnel category
A military personnel category is a classification that groups service members based on roles, ranks, duties, or service status within the armed forces.
-
D.
UNSC military personnel
UNSC military personnel are the organized, trained, and equipped members of the United Nations Space Command’s armed forces responsible for conducting space, air, land, and naval operations to defend humanity and its interests.
-
E.
component of the United States Army
A component of the United States Army is a major organizational subdivision, such as the Active Army, Army National Guard, or Army Reserve, that collectively contributes to the Army’s overall mission and capabilities.
- 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.