Triple
T12930265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imphal River |
E309357
|
entity |
| Predicate | hasRiskOf |
P62537
|
FINISHED |
| Object | seasonal flooding in Manipur |
—
|
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: seasonal flooding in Manipur | Statement: [Imphal River, hasRiskOf, seasonal flooding in Manipur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiskOf Context triple: [Imphal River, hasRiskOf, seasonal flooding in Manipur]
-
A.
hasWithdrawalRisk
Indicates that discontinuing or reducing something is associated with a risk of withdrawal effects or adverse reactions.
-
B.
hasCountryOfRisk
Indicates that an entity is associated with a country where it faces significant exposure, vulnerability, or potential risk.
-
C.
riskElement
chosen
Indicates that one entity is a risk-related component, factor, or contributor associated with another entity within a risk context.
-
D.
riskTaken
Indicates that an entity has undertaken an action or decision involving exposure to potential loss, harm, or uncertainty.
-
E.
hasHazardLevel
Indicates that an entity is associated with a specified degree or category of risk or danger.
- 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97245b6408190816d9b7e314eb51a |
completed | April 10, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69d96fab4d0881909a7a4d66bab9aa85 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:42 p.m.