Triple
T32038177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fraunhofer Defense and Security research portfolio |
E818149
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | applied research program |
C59504
|
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: applied research program Context triple: [Fraunhofer Defense and Security research portfolio, instanceOf, applied research program]
-
A.
scientific research support program
A scientific research support program is an organized initiative that provides resources, funding, infrastructure, and guidance to facilitate the planning, execution, and dissemination of scientific studies.
-
B.
university research program
A university research program is an organized, often interdisciplinary initiative within a higher education institution that supports systematic investigation, innovation, and scholarly inquiry in specific fields or themes.
-
C.
research center program
A research center program is an organized initiative within a research institution that coordinates projects, resources, and collaborations to advance inquiry and innovation in a specific field or set of related disciplines.
-
D.
scientific research programme
A scientific research programme is a structured, long-term framework of theories, methods, and guiding assumptions that directs and organizes systematic investigation within a particular field of inquiry.
-
E.
applied research institute
An applied research institute is an organization that conducts practical, problem-focused scientific and technical investigations to develop solutions, technologies, or processes for real-world applications.
- F. None of above. chosen
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.