Triple
T16916460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brisbane River Bridge (historical planning name) |
E410332
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | planned bridge project |
C22890
|
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: planned bridge project Context triple: [Brisbane River Bridge (historical planning name), instanceOf, planned bridge project]
-
A.
proposed bridge
chosen
A proposed bridge is a planned but not yet constructed structure designed to span a physical obstacle, documented through preliminary designs, locations, and specifications for evaluation and approval.
-
B.
infrastructure project
An infrastructure project is a large-scale, organized effort to plan, design, and construct foundational physical systems—such as transportation, utilities, and public facilities—that support a community’s or region’s economic and social activities.
-
C.
river bridge
A river bridge is a structure built to span a river, providing a stable pathway for vehicles, pedestrians, or rail traffic to cross from one bank to the other.
-
D.
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.
-
E.
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.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:30 a.m.