Triple
T2436540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teesta River |
E52973
|
entity |
| Predicate | floodRiskRegion |
P12640
|
FINISHED |
| Object | northern Bangladesh |
—
|
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: northern Bangladesh | Statement: [Teesta River, floodRiskRegion, northern Bangladesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floodRiskRegion Context triple: [Teesta River, floodRiskRegion, northern Bangladesh]
-
A.
hasFloodRisk
chosen
Indicates that an entity is exposed to a potential or expected risk of flooding under certain conditions.
-
B.
hasFloodplain
Indicates that an area or location lies within the floodplain associated with a particular water body or flooding source.
-
C.
hasFloodplainType
Indicates that an area or location is associated with a specific type or classification of floodplain.
-
D.
floodCause
Indicates that one entity is the cause or source of a flood affecting another entity or area.
-
E.
hasSeasonalFlooding
Indicates that an area regularly experiences flooding during specific, recurring times of the year.
- 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_69ab4959bcc0819083246f9fb10439e3 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcebf7cac8190889e6890d72c256c |
completed | March 7, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69abc5ac11b081908ce6a506e81a742a |
completed | March 7, 2026, 6:29 a.m. |
Created at: March 6, 2026, 9:43 p.m.