Triple
T4840767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jan Nowak-Jeziorański |
E108173
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II courier |
C3437
|
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 courier Context triple: [Jan Nowak-Jeziorański, instanceOf, World War II courier]
-
A.
World War II resistance member
chosen
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.
-
B.
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.
-
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.
Soviet agent
A Soviet agent is an individual who covertly gathers, transmits, or influences information and activities on behalf of the Soviet state’s intelligence or security services, often operating under false identities or clandestine arrangements.
-
E.
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.
- 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_69bd43fbe444819085cb970706ef73f7 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:25 p.m.