Triple
T35856209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morton Sobell |
E1036511
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | American spy for the Soviet Union |
C12229
|
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: American spy for the Soviet Union Context triple: [Morton Sobell, instanceOf, American spy for the Soviet Union]
-
A.
Soviet agent
chosen
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.
-
B.
Espionage specialist
An espionage specialist is a covert operations expert skilled in intelligence gathering, infiltration, and manipulation to obtain sensitive information while remaining undetected.
-
C.
Cuban intelligence officer
A Cuban intelligence officer is a government agent responsible for gathering, analyzing, and protecting sensitive information to support Cuba’s national security and strategic interests, often through covert operations and counterintelligence activities.
-
D.
Office of Strategic Services officer
An Office of Strategic Services officer is a World War II-era U.S. intelligence operative responsible for gathering information, conducting espionage and covert operations, and supporting resistance movements behind enemy lines.
-
E.
Secret Service agent
A Secret Service agent is a highly trained federal law enforcement officer responsible for protecting national leaders and safeguarding the integrity of the nation’s financial and critical security systems.
- 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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.