Triple
T35313465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ULTRA |
E1019840
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Allied intelligence program |
C13392
|
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: Allied intelligence program Context triple: [ULTRA, instanceOf, Allied intelligence program]
-
A.
CIA program
A CIA program is an organized, often covert initiative or operation designed and managed by the Central Intelligence Agency to achieve specific intelligence, security, or foreign policy objectives.
-
B.
World War II project
A World War II project is a structured investigation or creative work that explores specific aspects of the Second World War—such as events, people, technology, or impacts—using historical sources to analyze and present findings.
-
C.
Office of Strategic Services unit
An Office of Strategic Services unit is a specialized World War II-era U.S. intelligence and covert operations group responsible for espionage, sabotage, and support to resistance movements behind enemy lines.
-
D.
espionage-supported scientific project
An espionage-supported scientific project is a research initiative that covertly acquires, protects, or manipulates scientific knowledge and technology through intelligence-gathering and clandestine operations to gain strategic advantage.
-
E.
signals intelligence program
chosen
A signals intelligence program is a coordinated set of activities, technologies, and procedures designed to collect, process, analyze, and exploit electronic signals and communications for intelligence and security purposes.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.