Triple
T9922298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic hurricane season |
E187824
|
entity |
| Predicate | stormNamingConvention |
P2555
|
FINISHED |
| Object | rotating lists of given names |
—
|
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: rotating lists of given names | Statement: [Atlantic hurricane season, stormNamingConvention, rotating lists of given names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stormNamingConvention Context triple: [Atlantic hurricane season, stormNamingConvention, rotating lists of given names]
-
A.
stormNameList
Indicates that a storm is included in a designated list of named storms.
-
B.
namingStructure
chosen
Indicates a relationship where one entity defines, organizes, or constrains the naming or label format used for another entity.
-
C.
numberOfNamedStorms
Indicates the total count of distinct storms that have been formally assigned names within a specified context or period.
-
D.
typicalStormType
Indicates the kind of storm that is most commonly or characteristically associated with a given context or location.
-
E.
हवामान
Indicates a relationship involving weather conditions or atmospheric state affecting entities or events.
- 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.