Triple
T24213797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Section V of MI6 |
E600629
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | counter-espionage branch |
C548
|
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: counter-espionage branch Context triple: [Section V of MI6, instanceOf, counter-espionage branch]
-
A.
intelligence agency division
chosen
A specialized organizational unit within an intelligence agency responsible for focused functions such as collection, analysis, operations, or support in pursuit of national security objectives.
-
B.
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.
-
C.
state security agency
A state security agency is a government organization responsible for protecting national security through intelligence gathering, counterintelligence, and enforcement activities aimed at preventing internal and external threats.
-
D.
Espionage specialist
An espionage specialist is a covert operations expert skilled in intelligence gathering, infiltration, and manipulation to obtain sensitive information while remaining undetected.
-
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_69e2953344c48190875730c7d52112a0 |
completed | April 17, 2026, 8:16 p.m. |
Created at: April 17, 2026, 11:57 p.m.