Triple
T13091744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ultra intelligence |
E310478
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military 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: military intelligence program Context triple: [Ultra intelligence, instanceOf, military intelligence program]
-
A.
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.
-
B.
military program
A military program is an organized set of defense-related activities, projects, or initiatives designed to develop, maintain, or enhance a nation's armed forces capabilities and readiness.
-
C.
counterintelligence program
A counterintelligence program is an organized set of activities and measures designed to detect, prevent, and neutralize espionage, sabotage, and other intelligence threats posed by foreign or hostile entities.
-
D.
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.
-
E.
military intelligence discipline
A military intelligence discipline is a specialized field within military operations focused on collecting, analyzing, and disseminating information about adversaries, terrain, and other factors to support strategic, operational, and tactical decision-making.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
Created at: April 9, 2026, 9:03 p.m.