Triple
T14301496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Nishnabotna River |
E354573
|
entity |
| Predicate | hasRiparianZone |
P113686
|
FINISHED |
| Object | agricultural land |
—
|
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: agricultural land | Statement: [West Nishnabotna River, hasRiparianZone, agricultural land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiparianZone Context triple: [West Nishnabotna River, hasRiparianZone, agricultural land]
-
A.
hasNearbyWetlandRegion
Indicates that a given location or area is situated close to, or in the vicinity of, a wetland region.
-
B.
hasFloodplains
Indicates that an area or region includes land that is subject to flooding, typically adjacent to a river or water body.
-
C.
containsWetland
Indicates that one area or region includes within its boundaries a wetland ecosystem.
-
D.
hasFloodplain
Indicates that an area or location lies within the floodplain associated with a particular water body or flooding source.
-
E.
hasProtectedWatershed
Indicates that an entity possesses or is associated with a watershed area that is legally or formally protected for conservation or resource management purposes.
- 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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de717fc2348190bb6ba3109bd2871f |
completed | April 14, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:11 a.m.