Triple
T20526401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Ajax |
E503947
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | MI6 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: MI6 operation Context triple: [Operation Ajax, instanceOf, MI6 operation]
-
A.
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.
-
B.
Special Operations Executive agent
A Special Operations Executive agent is a covert operative trained to conduct sabotage, espionage, and support for resistance movements behind enemy lines during wartime.
-
C.
British intelligence agency
A British intelligence agency is a government organization responsible for gathering, analyzing, and acting on information to protect the United Kingdom’s national security and interests at home and abroad.
-
D.
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.
-
E.
British intelligence officer
A British intelligence officer is a government agent responsible for gathering, analyzing, and acting on sensitive information to protect the United Kingdom’s national security and strategic 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_69e0b4b3a6e08190ae663701f50fab8e |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:37 a.m.