Triple
T23225005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 North India floods |
E580989
|
entity |
| Predicate | economicDamageCurrency |
P40035
|
FINISHED |
| Object | INR |
—
|
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: INR | Statement: [2013 North India floods, economicDamageCurrency, INR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: economicDamageCurrency Context triple: [2013 North India floods, economicDamageCurrency, INR]
-
A.
economicDamage
Indicates that one entity causes or experiences financial loss, harm, or negative economic impact as a result of another entity or event.
-
B.
economicDamageApprox
Indicates that one entity has caused or is associated with an estimated or approximate amount of economic damage to another entity or system.
-
C.
economicDamageRank
Indicates the relative severity or position of an entity in terms of the economic damage it causes or experiences compared to others.
-
D.
currencyOfDamageCost
chosen
Indicates the monetary currency in which a specified damage cost amount is expressed.
-
E.
economicCost
Indicates the financial burden, expense, or resource expenditure associated with an action, event, or relationship between entities.
- 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_69e246043c48819089bae72c9a9c306c |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f1922d30b08190a3c54bab58f5c8e7 |
completed | April 29, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:08 p.m.