Triple
T87578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSF Proposal and Award Policies and Procedures Guide (PAPPG) |
E1760
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | National Science Foundation policy |
C3
|
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: National Science Foundation policy Context triple: [NSF Proposal and Award Policies and Procedures Guide (PAPPG), instanceOf, National Science Foundation policy]
-
A.
science policy document
chosen
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 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.
-
C.
United States federal policy
United States federal policy is the body of laws, regulations, and official actions enacted or implemented by the federal government to address national issues and guide public and private behavior across the country.
-
D.
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.
-
E.
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.
- 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_69a24c8150408190910a693eb51c1f71 |
completed | Feb. 28, 2026, 2:01 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.