Triple
T6502670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SOE |
E148929
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | secret British World War II organization |
C3529
|
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: secret British World War II organization Context triple: [SOE, instanceOf, secret British World War II organization]
-
A.
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.
-
B.
secret government agency
A secret government agency is a covert, officially sanctioned organization that operates outside public scrutiny to conduct sensitive intelligence, security, or special operations in the interest of national or global objectives.
-
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.
covert intelligence organization
chosen
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.
-
E.
Polish resistance organization
A Polish resistance organization is a clandestine group formed in Poland to oppose and undermine occupying or oppressive regimes through coordinated political, military, and intelligence activities.
- 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_69c687e9ad288190bae5bcac9c8ac855 |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 1:42 p.m.