Triple
T28536598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Idalia |
E722178
|
entity |
| Predicate | replacedStatus |
P180711
|
FINISHED |
| Object | retired hurricane name |
—
|
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: retired hurricane name | Statement: [Idalia, replacedStatus, retired hurricane name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedStatus Context triple: [Idalia, replacedStatus, retired hurricane name]
-
A.
replacedBecause
Indicates that one entity has been substituted for another specifically due to a particular reason or cause.
-
B.
replacedDuring
Indicates that one entity took the place of another entity during a specified time period or interval.
-
C.
reReleaseStatus
Indicates the release state or condition of something in relation to a prior or original release.
-
D.
replacedOrConsolidated
Indicates that one entity has been superseded, merged, or absorbed into another, such that the original is no longer used independently.
-
E.
replacedStandard
Indicates that one standard has been superseded or taken the place of another standard.
- F. None of above. chosen
Provenance (4 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
| PDg | Predicate description generation | batch_69f74c6fa6548190b03935f65429a24e |
completed | May 3, 2026, 1:23 p.m. |
Created at: April 28, 2026, 3:32 a.m.