Triple
T20805156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurricane Wilma |
E512135
|
entity |
| Predicate | basinRecord |
P141878
|
FINISHED |
| Object | strongest Atlantic hurricane by central pressure |
—
|
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: strongest Atlantic hurricane by central pressure | Statement: [Hurricane Wilma, basinRecord, strongest Atlantic hurricane by central pressure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basinRecord Context triple: [Hurricane Wilma, basinRecord, strongest Atlantic hurricane by central pressure]
-
A.
basin
Indicates a geographic area where surface water drains into a common outlet, such as a river, lake, or ocean.
-
B.
basinFeature
Indicates that one entity is a physical feature or component located within or forming part of a basin.
-
C.
basinState
Indicates that a state contains or encompasses the drainage basin or watershed of a particular river or water system.
-
D.
basinType
Indicates the specific kind or classification of a basin associated with an entity (e.g., by form, function, or hydrological role).
-
E.
resourceBasin
Indicates a relationship where a basin serves as a source or reservoir of resources for another entity or area.
- 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_69e0b4cc69f481908e98751e697b9df4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2ce6420819091792ffaa3c46c53 |
completed | April 21, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:40 p.m.