Triple
T21372855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brahmani River |
E527112
|
entity |
| Predicate | floodProneAreas |
P75660
|
FINISHED |
| Object | lower Brahmani delta region |
—
|
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: lower Brahmani delta region | Statement: [Brahmani River, floodProneAreas, lower Brahmani delta region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floodProneAreas Context triple: [Brahmani River, floodProneAreas, lower Brahmani delta region]
-
A.
hasFloodplains
chosen
Indicates that an area or region includes land that is subject to flooding, typically adjacent to a river or water body.
-
B.
hasFloodplain
Indicates that an area or location lies within the floodplain associated with a particular water body or flooding source.
-
C.
hasFloodRisk
Indicates that an entity is exposed to a potential or expected risk of flooding under certain conditions.
-
D.
inundatedRegion
Indicates that a region is covered or overwhelmed by water, typically due to flooding or heavy precipitation.
-
E.
hasFloodRiskRelevance
Indicates that something is pertinent to, affects, or is used in assessing the risk or likelihood of flooding.
- 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_69e0b51e80808190ba5cb05667af02a9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b0b18b2c81908e16beff92381160 |
completed | April 22, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:10 p.m.