Triple
T2561367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish POWs |
E57247
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Polish military personnel |
C9589
|
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: Polish military personnel Context triple: [Polish POWs, instanceOf, Polish military personnel]
-
A.
Polish military position
A Polish military position is an organized role or rank within Poland's armed forces, defined by specific duties, authority, and responsibilities in the national defense structure.
-
B.
German soldiers
German soldiers are military personnel serving in Germany’s armed forces, historically or presently, who are trained, organized, and equipped to conduct defense and combat operations under German command.
-
C.
American military personnel
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.
-
D.
Polish military history event
A Polish military history event is a significant occurrence involving Poland’s armed forces—such as battles, campaigns, uprisings, operations, or strategic decisions—that influenced the course of Poland’s national or military development.
-
E.
military personnel category
chosen
A military personnel category is a classification that groups service members based on roles, ranks, duties, or service status within the armed forces.
- 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_69ab4a4ef9008190a0e6d4422b9418b7 |
completed | March 6, 2026, 9:42 p.m. |
Created at: March 6, 2026, 9:48 p.m.