Triple
T6502780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vera Atkins |
E148931
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Special Operations Executive officer |
C1013
|
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: Special Operations Executive officer Context triple: [Vera Atkins, instanceOf, Special Operations Executive officer]
-
A.
intelligence officer
chosen
An intelligence officer is a professional responsible for collecting, analyzing, and disseminating sensitive information to support national security, military operations, or organizational decision-making.
-
B.
Waffen-SS officer
A Waffen-SS officer was a commissioned leader within Nazi Germany’s Waffen-SS, responsible for commanding combat units of this paramilitary organization that was deeply involved in war crimes and atrocities during World War II.
-
C.
director of intelligence agency
A director of an intelligence agency is the top executive responsible for overseeing intelligence operations, setting strategic priorities, managing resources, and advising national leaders on security threats and information.
-
D.
British military leader
A British military leader is a high-ranking officer from the United Kingdom responsible for planning, directing, and overseeing military operations and strategy, often commanding troops in national defense or international conflicts.
-
E.
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.
- 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_69c687e9ad288190bae5bcac9c8ac855 |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 1:42 p.m.