Triple
T14390737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birmingham and Fazeley Canal |
E356834
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 18th-century canal |
C33922
|
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: 18th-century canal Context triple: [Birmingham and Fazeley Canal, instanceOf, 18th-century canal]
-
A.
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.
-
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.
former canal
A former canal is a disused or decommissioned artificial waterway that once facilitated transportation, irrigation, or drainage but no longer serves its original function.
-
D.
18th-century building
An 18th-century building is a structure constructed between 1701 and 1800 that typically reflects the architectural styles, materials, and construction techniques of that period, such as Georgian, Baroque, or Neoclassical design.
-
E.
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.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:16 a.m.