Triple
T1743866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lech River |
E38291
|
entity |
| Predicate | hasFloodplainType |
P32041
|
FINISHED |
| Object | gravel floodplains |
—
|
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: gravel floodplains | Statement: [Lech River, hasFloodplainType, gravel floodplains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFloodplainType Context triple: [Lech River, hasFloodplainType, gravel floodplains]
-
A.
hasFloodplain
Indicates that an area or location lies within the floodplain associated with a particular water body or flooding source.
-
B.
hasFloodRisk
Indicates that an entity is exposed to a potential or expected risk of flooding under certain conditions.
-
C.
hasHydrologicalType
Indicates a relationship where an entity is classified according to its hydrological category or type (e.g., river, lake, aquifer).
-
D.
hasHydrologicalFunction
Indicates that something performs a role or action related to the movement, storage, or regulation of water within a hydrological system.
-
E.
hasWatershedCharacteristic
Indicates that a watershed possesses a specified characteristic, feature, or property.
- 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_69a8862b01a48190ab47209063af82d9 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab630e7d008190a8c673665d9672bb |
completed | March 6, 2026, 11:28 p.m. |
| PD | Predicate disambiguation | batch_69aa61c5a18481909bc49e0c54d64314 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab630cb34881908c9fb7ed5dedcd77 |
completed | March 6, 2026, 11:28 p.m. |
Created at: March 4, 2026, 7:31 p.m.