Triple
T29562316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackbriar operation |
E750070
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional covert 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: fictional covert operation Context triple: [Blackbriar operation, instanceOf, fictional covert 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.
CIA front company
A CIA front company is a seemingly legitimate business entity secretly created or controlled by the Central Intelligence Agency to provide cover, funding, logistics, or operational support for intelligence activities without revealing government involvement.
-
C.
fictional military program
A fictional military program is an imagined, often secretive initiative or project within an armed forces setting, designed to explore advanced technologies, strategies, or operations that drive the narrative in speculative or military-themed stories.
-
D.
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.
-
E.
Cold War operation
A Cold War operation is a covert or overt mission conducted by a state or its proxies during the Cold War era to advance strategic, ideological, or geopolitical objectives without escalating into full-scale direct conflict between superpowers.
- 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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 28, 2026, 5:20 p.m.