Triple
T1913227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tungabhadra River |
E38155
|
entity |
| Predicate | hasFloodplainUse |
P33899
|
FINISHED |
| Object | paddy cultivation |
—
|
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: paddy cultivation | Statement: [Tungabhadra River, hasFloodplainUse, paddy cultivation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFloodplainUse Context triple: [Tungabhadra River, hasFloodplainUse, paddy cultivation]
-
A.
hasFloodplain
Indicates that an area or location lies within the floodplain associated with a particular water body or flooding source.
-
B.
hasFloodplainType
Indicates that an area or location is associated with a specific type or classification of floodplain.
-
C.
hasWatershedUse
Indicates that a particular type of use, activity, or function is associated with or applied to a watershed.
-
D.
hasShorelineUse
Indicates that a geographic area or property is used for a particular type of activity or purpose along its shoreline.
-
E.
hasFloodRisk
Indicates that an entity is exposed to a potential or expected risk of flooding under certain conditions.
- F. None of above. chosen
Provenance (4 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_69a8862a26088190aae5243695aeefc0 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafeba3d88190afcce67483d8625b |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb34c4a64819096e12b152b84c334 |
completed | March 7, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:35 p.m.