Triple
T324305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PAPPG |
E6479
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | grant policy document |
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: grant policy document Context triple: [PAPPG, instanceOf, grant policy document]
-
A.
grant administration guide
A grant administration guide is a comprehensive reference that outlines the policies, procedures, and best practices for managing grants throughout their lifecycle, from application and award through implementation, reporting, and closeout.
-
B.
founding document
A founding document is an authoritative text that formally establishes an organization, institution, or state by defining its core principles, structure, and governing rules.
-
C.
legal pledge
A legal pledge is a formal commitment, often documented and enforceable by law, in which a party promises to fulfill specific obligations or refrain from certain actions, typically as security or assurance in a legal or contractual context.
-
D.
policy report
A policy report is a structured document that analyzes a specific issue, evaluates options, and presents evidence-based recommendations to guide decision-making by policymakers or stakeholders.
-
E.
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.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.