Triple
T24213798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Section V of MI6 |
E600629
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intelligence agency section |
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: intelligence agency section Context triple: [Section V of MI6, instanceOf, intelligence agency section]
-
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.
signals intelligence agency
A signals intelligence agency is an organization responsible for intercepting, analyzing, and exploiting electronic communications and signals to support national security, defense, and law enforcement objectives.
-
C.
intelligence community
The intelligence community is a collective network of government agencies and organizations responsible for gathering, analyzing, and disseminating information to support national security and foreign policy decision-making.
-
D.
domestic intelligence agency
A domestic intelligence agency is a government organization responsible for collecting, analyzing, and acting on information related to internal security threats within a country's borders, such as terrorism, espionage, and subversion.
-
E.
intelligence agency position
An intelligence agency position is a role within a governmental or authorized organization responsible for collecting, analyzing, and acting on sensitive information to support national security and policy objectives.
- 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.