Triple
T21910948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secretary’s Award for Exceptional Service |
E541055
|
entity |
| Predicate | frequencyOfConferral |
P2205
|
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: [Secretary’s Award for Exceptional Service, frequencyOfConferral, periodically]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequencyOfConferral Context triple: [Secretary’s Award for Exceptional Service, frequencyOfConferral, periodically]
-
A.
awardedFrequency
chosen
Indicates how often an award or recognition is given within a specified time period.
-
B.
conferenceFrequency
Indicates how often a conference or similar recurring event takes place within a given time period.
-
C.
conferredIn
Indicates that something (such as a degree, title, or honor) was formally granted or awarded within a particular context, event, or institution.
-
D.
numberOfGrants
Indicates the total count of grants associated with a given entity or context.
-
E.
traditionallyConferredBy
Indicates that something (such as a role, title, or honor) is customarily or historically granted or bestowed by a particular person, group, or institution.
- F. None of above.
Provenance (3 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_69e0c47c4b9c8190a5586a75f5f36453 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f121da36e88190b42b82641ec54a19 |
completed | April 28, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e6be9ebf4c8190892df1a8e1313f88 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:40 p.m.