Triple
T38136666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurricane Isaac |
E952368
|
entity |
| Predicate | damageUSD |
P25888
|
FINISHED |
| Object | 2400000000 |
—
|
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: 2400000000 | Statement: [Hurricane Isaac, damageUSD, 2400000000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: damageUSD Context triple: [Hurricane Isaac, damageUSD, 2400000000]
-
A.
economicDamageApprox
chosen
Indicates that one entity has caused or is associated with an estimated or approximate amount of economic damage to another entity or system.
-
B.
economicDamage
Indicates that one entity causes or experiences financial loss, harm, or negative economic impact as a result of another entity or event.
-
C.
currencyOfDamageCost
Indicates the monetary currency in which a specified damage cost amount is expressed.
-
D.
damageCostNote
Indicates a descriptive note or explanation associated with the cost of damage, providing contextual or clarifying information about that damage-related expense.
-
E.
economicDamageRank
Indicates the relative severity or position of an entity in terms of the economic damage it causes or experiences compared to others.
- 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_69f76f09a7148190a4b91c0bacdc127a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:21 p.m.