Triple
T498073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Framework Programmes for Research and Innovation |
E10339
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | science and technology policy instrument |
C2954
|
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: science and technology policy instrument Context triple: [Framework Programmes for Research and Innovation, instanceOf, science and technology policy instrument]
-
A.
science policy document
A science policy document is a formal written record that outlines principles, guidelines, and strategic decisions governing the conduct, funding, regulation, and societal integration of scientific research and innovation.
-
B.
science policy advisor
A science policy advisor analyzes scientific evidence and trends to inform, develop, and recommend policies that effectively address societal, technological, and environmental challenges.
-
C.
science agency
A science agency is an organization, typically governmental or intergovernmental, that funds, coordinates, and oversees scientific research and development to advance knowledge and inform policy.
-
D.
science policy official
A science policy official is a professional who develops, analyzes, and implements policies that guide the use, funding, and regulation of scientific research and technology in government or institutional settings.
-
E.
science and technology award
A science and technology award is a formal recognition given to individuals or organizations for outstanding achievements, innovations, or contributions in scientific research and technological development.
- 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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.