Triple
T17408869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Controlling Section |
E423293
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military deception 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: military deception organization Context triple: [London Controlling Section, instanceOf, military deception organization]
-
A.
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.
-
B.
CIA front company
A CIA front company is a seemingly legitimate business entity secretly created or controlled by the Central Intelligence Agency to provide cover, funding, logistics, or operational support for intelligence activities without revealing government involvement.
-
C.
military organization
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
-
D.
hoax organization
A hoax organization is a fictitious or misleading entity presented as a legitimate group or institution, typically created to deceive, satirize, or manipulate public perception.
-
E.
military recruitment organization
A military recruitment organization is an entity responsible for attracting, evaluating, and processing individuals for enlistment or commissioning into a nation's armed forces.
- 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:46 a.m.