Triple
T25161951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Maurice of Battenberg |
E626462
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War I military personnel killed in action |
C19727
|
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: World War I military personnel killed in action Context triple: [Prince Maurice of Battenberg, instanceOf, World War I military personnel killed in action]
-
A.
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).
-
B.
participant in World War I
chosen
A participant in World War I is any nation, military force, or individual actively involved in the political, military, or logistical operations of the global conflict between 1914 and 1918.
-
C.
World War I site
A World War I site is a historically significant location directly associated with events, operations, or impacts of the First World War, such as battlefields, trenches, memorials, cemeteries, or military installations.
-
D.
person killed in action
A person killed in action is an individual who dies while actively engaged in a military or combat operation.
-
E.
military leader of World War I
A military leader of World War I is a high-ranking officer or commander responsible for planning, directing, and overseeing large-scale military operations and strategies for a nation or alliance during the 1914–1918 global conflict.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:31 a.m.