Triple
T35299024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dilly |
E1019454
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II codebreaker |
C64353
|
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 codebreaker Context triple: [Dilly, instanceOf, World War II codebreaker]
-
A.
World War II code talkers
World War II code talkers were Indigenous military communicators, most famously Navajo Marines, who used their native languages to create unbreakable tactical codes for secure battlefield transmissions.
-
B.
World War II special forces
World War II special forces were elite, highly trained military units from various nations that conducted covert, high-risk operations such as sabotage, reconnaissance, and raids behind enemy lines to achieve strategic objectives.
-
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 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.
-
E.
World War II resistance operation
A World War II resistance operation is a covert, organized action conducted by underground groups in occupied territories to sabotage enemy forces, gather intelligence, and support Allied war efforts.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.