Triple
T38608338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romanesque bridge of Besalú |
E934407
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Romanesque bridge |
C1512
|
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: Romanesque bridge Context triple: [Romanesque bridge of Besalú, instanceOf, Romanesque bridge]
-
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.
arched bridge
An arched bridge is a structure that spans a physical obstacle using one or more curved arches that transfer loads primarily through compression into its supports.
-
C.
stone arch bridge
chosen
A stone arch bridge is a structure composed of curved stone arches that span a gap, using the compressive strength of masonry to support loads and provide passage over obstacles like rivers or valleys.
-
D.
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.
-
E.
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.
- 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_69f76eccd6d081909ccce171011739a1 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:32 p.m.