Triple
T5438200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hans-Georg von Friedeburg |
E122063
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | person involved in World War II |
C451
|
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: person involved in World War II Context triple: [Hans-Georg von Friedeburg, instanceOf, person involved in World War II]
-
A.
World War II veteran
chosen
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.
World War II resistance member
A World War II resistance member is an individual who clandestinely opposed Axis occupation or authoritarian regimes through activities such as sabotage, intelligence gathering, underground communication, and support for persecuted populations.
-
C.
World War II military role
A World War II military role represents a specific set of duties, responsibilities, and functions performed by individuals or units within the armed forces of nations involved in the conflict between 1939 and 1945.
-
D.
aspect of World War II
An aspect of World War II is a distinct thematic component—such as military strategy, political leadership, home-front life, technology, or ideology—that helps explain how the conflict was conducted, experienced, and remembered.
-
E.
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).
- 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_69bd46400768819092925d461c0b8432 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:07 p.m.