Triple
T34702141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Punt Road Bridge |
E1000402
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bridge in Melbourne |
C61939
|
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: bridge in Melbourne Context triple: [Punt Road Bridge, instanceOf, bridge in Melbourne]
-
A.
bridge in Sydney
A bridge in Sydney is a large engineered structure spanning a body of water or land to connect different parts of the city, facilitating transportation and often serving as a prominent architectural landmark.
-
B.
bridge in Perth, Western Australia
A bridge in Perth, Western Australia is a structural crossing—such as a road, rail, or pedestrian span—located within the Perth metropolitan area that connects separated land areas over obstacles like the Swan River, roads, or railways.
-
C.
bridge in New South Wales
A bridge in New South Wales is a constructed structure that spans physical obstacles such as waterways, roads, or valleys within the Australian state of New South Wales to provide a transportation route for vehicles, pedestrians, or rail.
-
D.
bridge in Bristol
A bridge in Bristol is a structural crossing—such as the iconic Clifton Suspension Bridge—spanning a river, road, or gorge within or near the city to connect different areas and support transport and movement.
-
E.
bridge in Helsinki
A bridge in Helsinki is a structural crossing—often combining functional Nordic engineering with minimalist design—that spans water or land to connect different parts of the city’s urban and coastal landscape.
- 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_69f76dab937881909c86f1b9ad50445f |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.