Triple
T28989646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Bridge |
E734787
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic bridge section |
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: historic bridge section Context triple: [Old Bridge, instanceOf, historic bridge section]
-
A.
ancient bridge
An ancient bridge is a historically significant structure built in antiquity to span a physical obstacle such as a river or valley, often showcasing the engineering techniques, materials, and cultural aesthetics of its era.
-
B.
historic gateway and bridge
A historic gateway and bridge is an architectural structure that combines a monumental entrance passage with a spanning construction over a physical obstacle, often serving both defensive and ceremonial functions while facilitating transit.
-
C.
historic building section
A historic building section is a vertical cut-through representation of an older, culturally or architecturally significant structure that reveals its internal organization, construction methods, and spatial relationships over time.
-
D.
heritage-listed bridge
chosen
A heritage-listed bridge is a historically or culturally significant bridge that has been officially recognized and protected for its architectural, engineering, or social value.
-
E.
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.
- 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_69f05b0dd9b481908b7901e1c95ff6b2 |
completed | April 28, 2026, 7 a.m. |
Created at: April 28, 2026, 9:16 a.m.