Triple
T37505004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niger uranium forgeries |
E932067
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intelligence controversy |
C18730
|
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 controversy Context triple: [Niger uranium forgeries, instanceOf, intelligence controversy]
-
A.
intelligence leak
An intelligence leak is the unauthorized disclosure of sensitive or classified information, often compromising operations, sources, or national security.
-
B.
controversy
chosen
Controversy is a state of public disagreement or heated debate arising from conflicting opinions, values, or interpretations about a particular issue, event, or decision.
-
C.
intelligence directive
An intelligence directive is a formal instruction or guiding framework that defines the objectives, priorities, and constraints for the collection, analysis, and dissemination of intelligence information.
-
D.
public policy controversy
A public policy controversy is a sustained, often polarized dispute among stakeholders over the goals, design, implementation, or consequences of government actions or regulations.
-
E.
intelligence front
An intelligence front is an ostensibly legitimate organization or entity that covertly serves as a cover for intelligence-gathering, espionage, or other clandestine 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.