Triple
T32781463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lombardy irrigation network |
E838365
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | irrigation network |
C58540
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: irrigation network Context triple: [Lombardy irrigation network, instanceOf, irrigation network]
-
A.
irrigated district
An irrigated district is a geographically defined area where water is systematically supplied and managed, typically through infrastructure like canals and pipelines, to support agricultural production and related land uses.
-
B.
irrigation organization
An irrigation organization is an entity that plans, manages, and coordinates the distribution and maintenance of water resources and infrastructure for agricultural or landscape irrigation within a defined area.
-
C.
irrigation command area
An irrigation command area is the total land surface that can be supplied with water from a specific irrigation system or source under its designed operating conditions.
-
D.
irrigation dam
An irrigation dam is a barrier constructed across a watercourse to store and regulate water specifically for agricultural use, enabling controlled distribution to fields and crops.
-
E.
heritage irrigation system
A heritage irrigation system is a historically significant network of water management structures and practices preserved for their cultural, technological, and agricultural value.
- F. None of above. chosen
Provenance (1 batch)
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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:14 a.m.