Triple
T13943840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marble Bridge |
E335327
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 18th-century bridge |
C9591
|
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: 18th-century bridge Context triple: [Marble Bridge, instanceOf, 18th-century bridge]
-
A.
19th-century bridge
A 19th-century bridge is a transportation structure built during the 1800s that typically reflects the era’s industrial advances in materials and engineering, such as iron, steel, and improved masonry techniques.
-
B.
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.
-
C.
18th-century building
chosen
An 18th-century building is a structure constructed between 1701 and 1800 that typically reflects the architectural styles, materials, and construction techniques of that period, such as Georgian, Baroque, or Neoclassical design.
-
D.
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.
-
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.
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_69d81c6081b88190b53e317c3370c8fe |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:17 p.m.