Triple
T10579350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grafton Bridge (rail‑road bridge over Clarence River) |
E249693
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heritage-listed bridge |
C28274
|
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: heritage-listed bridge Context triple: [Grafton Bridge (rail‑road bridge over Clarence River), instanceOf, heritage-listed bridge]
-
A.
cast-iron bridge
A cast-iron bridge is a structure whose primary load-bearing elements are made from cast iron, typically featuring modular, prefabricated components assembled to span a gap such as a river or roadway.
-
B.
covered bridge
A covered bridge is a typically wooden, roofed structure that spans a waterway or gap, enclosing its roadway to protect the supporting framework from weather and extend its lifespan.
-
C.
ornamental bridge
An ornamental bridge is a decorative structure, often smaller in scale than functional bridges, designed primarily to enhance the aesthetic appeal of a landscape or garden while sometimes providing light pedestrian passage.
-
D.
causeway-style bridge
A causeway-style bridge is a low, often long roadway structure built across water, wetlands, or low-lying terrain, typically supported by embankments or short spans rather than tall piers.
-
E.
wrought-iron bridge
A wrought-iron bridge is a structure for spanning physical obstacles, such as rivers or roads, whose primary load-bearing elements are made from wrought iron, valued historically for its toughness, malleability, and resistance to fatigue.
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
Created at: April 6, 2026, 12:38 p.m.