Triple
T35056908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qanats |
E1011492
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | traditional water management system |
C43250
|
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: traditional water management system Context triple: [Qanats, instanceOf, traditional water management system]
-
A.
water management structure
A water management structure is a constructed facility or system designed to control, store, convey, or regulate the quantity and movement of water in natural or built environments.
-
B.
surface water system
A surface water system is a network of natural and engineered features—such as rivers, lakes, reservoirs, and channels—through which water collects, flows, is stored, and is managed on the Earth’s surface.
-
C.
water supply system
A water supply system is an interconnected network of sources, treatment facilities, storage structures, and distribution pipelines designed to deliver safe and reliable water to end users.
-
D.
heritage irrigation system
chosen
A heritage irrigation system is a historically significant network of water management structures and practices preserved for their cultural, technological, and agricultural value.
-
E.
water level management practice
A water level management practice is a coordinated set of methods and operations used to monitor, control, and adjust water levels in natural or engineered systems to meet ecological, safety, and resource-use objectives.
- F. None of above.
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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.