Triple
T24213824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Directorate of Military Intelligence |
E600630
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British military intelligence agency |
C3530
|
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: British military intelligence agency Context triple: [Directorate of Military Intelligence, instanceOf, British military intelligence agency]
-
A.
British intelligence agency
chosen
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.
-
B.
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.
-
C.
government agency of the United Kingdom
A government agency of the United Kingdom is an official public body established by the UK government to carry out specific administrative, regulatory, or service-delivery functions on its behalf.
-
D.
British paramilitary police force
A British paramilitary police force is a law enforcement body organized, trained, and equipped along military lines to perform policing, public order, and security duties while operating under civilian authority.
-
E.
British government department
A British government department is an administrative unit of the UK government responsible for developing and implementing public policy and delivering specific services within a defined area of national governance.
- 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.