Triple
T36500795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waterloo Bridge |
E899320
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | reinforced concrete bridge |
C9757
|
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: reinforced concrete bridge Context triple: [Waterloo Bridge, instanceOf, reinforced concrete bridge]
-
A.
reinforced-concrete bridge
A reinforced-concrete bridge is a structural system in which concrete and embedded steel reinforcement work together to safely carry and distribute loads across a span.
-
B.
reinforced-concrete bridge
chosen
A reinforced-concrete bridge is a structural system in which concrete and embedded steel reinforcement work together to safely span obstacles and carry traffic loads over a defined distance.
-
C.
concrete bridge
A concrete bridge is a structure built primarily from reinforced or prestressed concrete to span physical obstacles such as roads, rivers, or valleys, providing a durable pathway for vehicles, pedestrians, or rail traffic.
-
D.
concrete bridge
A concrete bridge is a structure built primarily from reinforced or prestressed concrete to span physical obstacles such as roads, rivers, or valleys, providing a durable and stable pathway for transportation.
-
E.
steel and concrete bridge
A steel and concrete bridge is a structural system that uses steel components for tensile and flexural strength combined with concrete elements for compressive resistance and durability to span physical obstacles such as roads, rivers, or valleys.
- 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_69f76e5b92088190933afda3f7531dd4 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.