Triple
T23281269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COINTELPRO |
E588869
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | covert government operation |
C35775
|
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 government operation Context triple: [COINTELPRO, instanceOf, covert government operation]
-
A.
covert intelligence operation
chosen
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.
-
B.
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.
-
C.
covert intelligence organization
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.
-
D.
secret government agency
A secret government agency is a covert, officially sanctioned organization that operates outside public scrutiny to conduct sensitive intelligence, security, or special operations in the interest of national or global objectives.
-
E.
Central Intelligence Agency operation
A Central Intelligence Agency operation is a covert or clandestine activity planned, authorized, and executed by the CIA to collect intelligence, influence events, or protect U.S. national security interests, often involving secrecy, specialized tradecraft, and coordination with domestic or foreign partners.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 4:57 p.m.