Triple
T9922316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic hurricane season |
E187824
|
entity |
| Predicate | forecastProduct |
P34023
|
FINISHED |
| Object | seasonal hurricane outlook |
—
|
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: seasonal hurricane outlook | Statement: [Atlantic hurricane season, forecastProduct, seasonal hurricane outlook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forecastProduct Context triple: [Atlantic hurricane season, forecastProduct, seasonal hurricane outlook]
-
A.
providesForecastFor
Indicates that one entity supplies or delivers a forecast (such as a prediction or projection) specifically concerning another entity.
-
B.
forecastUsing
Indicates that one entity generates or derives a forecast by using information, methods, or data from another entity.
-
C.
weatherCondition
Indicates the type of atmospheric state or weather pattern (e.g., sunny, rainy, snowy) affecting a location or time period.
-
D.
typeOfForecasts
chosen
Indicates the specific kinds or categories of forecasts associated with or produced by an entity.
-
E.
drivesWeather
Indicates that one factor or process causally influences or determines weather conditions.
- 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_69ca82b22a688190b52c75bd48429c10 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb56c7da88190ac37986a2e766b1e |
completed | April 2, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69cd1d90b8a8819081748f129c0c6ab6 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:42 p.m.