Triple
T17618987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holytown railway viaduct |
E429659
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multi-arch bridge |
C39447
|
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: multi-arch bridge Context triple: [Holytown railway viaduct, instanceOf, multi-arch bridge]
-
A.
through-arch bridge
A through-arch bridge is a type of arch bridge in which the deck passes between the arches, with the arch ribs rising above the roadway and connected by vertical or diagonal hangers that support the deck.
-
B.
multipurpose bridge
A multipurpose bridge is a structural crossing designed to support multiple concurrent uses—such as vehicular traffic, pedestrians, cyclists, utilities, and sometimes public spaces or transit systems—within a single integrated infrastructure.
-
C.
cross-distribution Linux framework
A cross-distribution Linux framework is a software layer or toolkit designed to run consistently across multiple Linux distributions by abstracting away distro-specific differences in packaging, configuration, and system services.
-
D.
bridge approach
A bridge approach is the section of roadway that transitions between the ground and the main span of a bridge, providing a smooth and stable connection for vehicles and pedestrians.
-
E.
private bridge
A private bridge is a non-publicly owned structure that spans a physical obstacle, such as a river or road, to provide controlled access exclusively for specific individuals, properties, or organizations.
- 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:51 a.m.