Triple
T32038178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fraunhofer Defense and Security research portfolio |
E818149
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defense and security research program |
C10566
|
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: defense and security research program Context triple: [Fraunhofer Defense and Security research portfolio, instanceOf, defense and security research program]
-
A.
defense research agency
A defense research agency is an organization that conducts scientific and technological research to develop advanced capabilities, systems, and knowledge in support of national security and military objectives.
-
B.
defence research laboratory
A defence research laboratory is a specialized facility dedicated to developing, testing, and evaluating technologies, systems, and methodologies to enhance national security and military capabilities.
-
C.
missile defense program
A missile defense program is an organized system of technologies, policies, and operations designed to detect, track, intercept, and neutralize incoming missiles before they reach their intended targets.
-
D.
military program
chosen
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.
-
E.
military rearmament program
A military rearmament program is a coordinated, government-directed initiative to expand, modernize, or restore a nation’s armed forces and weaponry in response to strategic, political, or security objectives.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:19 a.m.