Triple
T21252881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurricane Gamma |
E523788
|
entity |
| Predicate | occurrenceOrderInSeason |
P51004
|
FINISHED |
| Object | late-season storm |
—
|
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: late-season storm | Statement: [Hurricane Gamma, occurrenceOrderInSeason, late-season storm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occurrenceOrderInSeason Context triple: [Hurricane Gamma, occurrenceOrderInSeason, late-season storm]
-
A.
occurredInSeason
Indicates that an event or occurrence took place during a specific season within a temporal sequence (such as a TV show season or sports season).
-
B.
positionInSeason
chosen
Indicates the specific ordinal placement or ranking of something within the sequence of items in a season.
-
C.
seasonSequence
Indicates the ordered succession relationship between seasons, specifying which season follows or precedes another in a temporal sequence.
-
D.
seasonAppearance
Indicates that an entity appears in, or is present during, a particular season within a series or sequence.
-
E.
serialNumberInSeason
Indicates the position or sequence number that something holds within a particular season.
- 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_69e0b5146c108190adc9adb73e90abff |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7359f5b408190b951adddba83c97a |
completed | April 21, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:57 p.m.