Triple
T15749596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarnowskie Góry water management system |
E381812
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic hydraulic engineering system |
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 engineering system Context triple: [Tarnowskie Góry water management system, instanceOf, historic hydraulic engineering system]
-
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.
Renaissance aqueduct
A Renaissance aqueduct is a monumental water-conveyance structure that revives and refines classical Roman engineering principles to transport water over long distances using arches, channels, and gravity-driven flow.
-
D.
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.
-
E.
levee system
A levee system is an integrated network of embankments, floodwalls, and related structures designed to contain or redirect water to protect land and infrastructure from flooding.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:46 a.m.