Triple
T11401073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C&O Canal |
E270109
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 19th-century waterway |
C26460
|
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: 19th-century waterway Context triple: [C&O Canal, instanceOf, 19th-century waterway]
-
A.
19th-century infrastructure
19th-century infrastructure encompasses the transportation, communication, and utility systems—such as railways, canals, telegraph networks, roads, and early urban services—built during the 1800s that enabled industrialization and expanded economic and social connectivity.
-
B.
19th-century bridge
A 19th-century bridge is a transportation structure built during the 1800s that typically reflects the era’s industrial advances in materials and engineering, such as iron, steel, and improved masonry techniques.
-
C.
baroque waterway
A baroque waterway is an ornately designed canal or watercourse, often integrated into grand landscapes or urban plans, characterized by elaborate curves, decorative features, and dramatic visual perspectives typical of the Baroque style.
-
D.
navigable waterway
A navigable waterway is a natural or artificial body of water, such as a river, canal, or channel, that is deep and wide enough for vessels to travel safely for transportation or commerce.
-
E.
engineered waterway
chosen
An engineered waterway is a human-made or heavily modified channel or system designed to control, convey, or manage water for purposes such as navigation, irrigation, drainage, flood control, or power generation.
- 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:34 p.m.