Triple
T23320188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | falua |
E591128
|
entity |
| Predicate | riskAdaptation |
P13964
|
FINISHED |
| Object | typhoon-prone waters |
—
|
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: typhoon-prone waters | Statement: [falua, riskAdaptation, typhoon-prone waters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riskAdaptation Context triple: [falua, riskAdaptation, typhoon-prone waters]
-
A.
riskTaken
Indicates that an entity has undertaken an action or decision involving exposure to potential loss, harm, or uncertainty.
-
B.
riskManagement
chosen
Indicates the implementation of strategies and actions to identify, assess, and mitigate potential risks associated with an entity or activity.
-
C.
riskSensitivity
Indicates how strongly an entity’s decisions or behavior change in response to potential risk or uncertainty.
-
D.
riskElement
Indicates that one entity is a risk-related component, factor, or contributor associated with another entity within a risk context.
-
E.
riskPractice
Indicates that an entity engages in or is associated with a practice, behavior, or procedure that carries a potential for harm, loss, or adverse outcomes.
- 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_69e25d1effe4819096907f95f610dbff |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1978440888190b316664812105d60 |
completed | April 29, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:07 p.m.