Triple
T32153354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet underground apparatus in the United States |
E821215
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | covert intelligence network |
C3529
|
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: covert intelligence network Context triple: [Soviet underground apparatus in the United States, instanceOf, covert intelligence network]
-
A.
covert intelligence organization
chosen
A covert intelligence organization is a secretive entity that gathers, analyzes, and acts on sensitive information through clandestine methods to influence or protect national or organizational interests.
-
B.
covert intelligence operation
A covert intelligence operation is a secretive, state-directed activity designed to gather information or influence events without revealing the sponsor’s identity or involvement.
-
C.
covert operative
A covert operative is a highly trained individual who conducts secret missions and gathers sensitive information while maintaining a concealed identity and minimizing detection.
-
D.
covert program
A covert program is a secretive, often unauthorized software or initiative designed to operate hidden from normal detection or oversight to achieve specific, typically sensitive objectives.
-
E.
colonial intelligence organization
A colonial intelligence organization is a state-backed agency operating within or across colonies to gather, analyze, and exploit information for maintaining imperial control, managing local populations, and advancing the colonizing power’s political, military, and economic interests.
- 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_69f34905e098819082191a6922a6d607 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:32 a.m.