Triple
T32423533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. National Climate Assessments |
E828517
|
entity |
| Predicate | requiredFrequency |
P8512
|
FINISHED |
| Object | at least every four years |
—
|
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: at least every four years | Statement: [U.S. National Climate Assessments, requiredFrequency, at least every four years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredFrequency Context triple: [U.S. National Climate Assessments, requiredFrequency, at least every four years]
-
A.
recommendedUsageFrequency
Indicates how often something is advised or prescribed to be used within a given time period.
-
B.
usualFrequency
Indicates how often an action, event, or relationship typically occurs within a given time frame.
-
C.
serviceFrequencyType
Indicates how often a service occurs or is scheduled within a given time period.
-
D.
frequencyRequirement
chosen
Indicates a constraint specifying how often an action, event, or condition must occur within a given context or time frame.
-
E.
dealFrequency
Indicates how often a particular deal, transaction, or agreement occurs within a given period.
- 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fef8c3f2388190b995ec173512945a |
completed | May 9, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69fef65975608190960b78d27e806d4f |
completed | May 9, 2026, 8:54 a.m. |
Created at: May 1, 2026, 12:54 a.m.