Triple
T9848665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navajo Code Talkers |
E239407
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II code talkers |
C26967
|
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 II code talkers Context triple: [Navajo Code Talkers, instanceOf, World War II code talkers]
-
A.
Japanese military personnel of World War II
Individuals who served in the armed forces of the Empire of Japan during World War II, including the Imperial Japanese Army, Navy, and associated military organizations.
-
B.
wartime codename
A wartime codename is a deliberately chosen, often cryptic label used to conceal the true nature, identity, or objectives of military operations, units, technologies, or locations during conflict.
-
C.
World War II commando raid
A World War II commando raid is a small-scale, highly planned military operation conducted by specially trained troops to infiltrate enemy territory, achieve a specific tactical or strategic objective, and withdraw quickly, often relying on surprise and stealth.
-
D.
World War II technology
World War II technology encompasses the advanced weapons, vehicles, communication systems, and scientific innovations developed and deployed during the conflict, which significantly influenced both the war’s outcome and postwar technological progress.
-
E.
World War II supply line
A World War II supply line is the network of transportation routes, logistics operations, and support infrastructure used to move troops, equipment, fuel, and provisions to and from battlefronts during the war.
- F. None of above. chosen
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_69ca84e4fdc08190a624425bcef98665 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:34 p.m.