Triple
T7370156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waterloo Village |
E169976
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | restored 19th-century canal town |
C8110
|
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: restored 19th-century canal town Context triple: [Waterloo Village, instanceOf, restored 19th-century canal town]
-
A.
restored waterway
A restored waterway is a previously degraded or altered river, stream, or canal that has been rehabilitated to improve its ecological function, water quality, and surrounding habitat while often enhancing recreational and aesthetic values.
-
B.
water town
A water town is a settlement built around and interlaced with waterways, where canals, rivers, or lakes play a central role in its transportation, architecture, and daily life.
-
C.
reconstructed historic site
chosen
A reconstructed historic site is a place where buildings, structures, or environments from the past have been rebuilt or significantly restored to approximate their original appearance and context for educational, commemorative, or touristic purposes.
-
D.
historic town centre
A historic town centre is the traditional core of a town characterized by preserved architecture, cultural landmarks, and public spaces that reflect its historical development and heritage.
-
E.
historic mill town
A historic mill town is a community that developed around water- or steam-powered mills, where industrial buildings, worker housing, and civic structures reflect the town’s past as a center of manufacturing and economic activity.
- 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_69c68a5bfaac81909ce7f001dfb70c76 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:07 p.m.