Triple
T14801491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamuna River (historical feed via aqueducts and channels) |
E347920
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic hydraulic infrastructure |
C3667
|
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: historic hydraulic infrastructure Context triple: [Yamuna River (historical feed via aqueducts and channels), instanceOf, historic hydraulic infrastructure]
-
A.
historic irrigation canal
A historic irrigation canal is a man-made waterway constructed in the past to divert and distribute water for agricultural use, often reflecting the engineering practices and socio-economic conditions of its time.
-
B.
historic infrastructure
chosen
Historic infrastructure comprises long-standing physical structures and systems—such as bridges, roads, canals, and railways—that were built in the past and continue to embody cultural, technological, and architectural significance.
-
C.
canal aqueduct
A canal aqueduct is a bridge-like structure that carries a navigable waterway over obstacles such as rivers, valleys, roads, or other canals.
-
D.
historic water well
A historic water well is a preserved or documented water source structure from the past that reflects the technological, cultural, and social practices of its time.
-
E.
canal infrastructure
Canal infrastructure encompasses the engineered systems, structures, and facilities—such as channels, locks, dams, embankments, and control mechanisms—designed to manage and support waterborne transport, irrigation, drainage, and water regulation along artificial waterways.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:31 a.m.