Triple
T87619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSF Proposal and Award Policies and Procedures Guide (PAPPG) |
E1760
|
entity |
| Predicate | isUpdated |
P4061
|
FINISHED |
| Object | periodically |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: periodically | Statement: [NSF Proposal and Award Policies and Procedures Guide (PAPPG), isUpdated, periodically]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUpdated Context triple: [NSF Proposal and Award Policies and Procedures Guide (PAPPG), isUpdated, periodically]
-
A.
wasReissued
Indicates that an item, such as a document or edition, has been issued again after its original release.
-
B.
amendedBy
Indicates that one entity has been modified, revised, or updated as a result of changes made by another entity.
-
C.
isFormerEntity
Indicates that an entity previously held a particular status, role, or identity but no longer does so.
-
D.
isLastMajor
Indicates that an entity is the final or most recent significant item or event within a defined sequence or set.
-
E.
wasSupersededBy
Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
- F. None of above. chosen
Provenance (4 batches)
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. |
| NER | Named-entity recognition | batch_69a2503d304c8190a0034ffa4a38a501 |
completed | Feb. 28, 2026, 2:17 a.m. |
| PD | Predicate disambiguation | batch_69a24eb6da2c8190a33d144d219f7abe |
completed | Feb. 28, 2026, 2:11 a.m. |
| PDg | Predicate description generation | batch_69a2503c12808190a3cbb7b171f466f0 |
completed | Feb. 28, 2026, 2:17 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.