Triple
T36247232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Ring Road |
E891697
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road infrastructure in Melbourne |
C2978
|
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: road infrastructure in Melbourne Context triple: [Western Ring Road, instanceOf, road infrastructure in Melbourne]
-
A.
street in Melbourne
A street in Melbourne is a public urban thoroughfare within the city’s grid or suburban layout, lined with a mix of residential, commercial, and cultural buildings, and shaped by the city’s distinctive tram network, laneways, and diverse neighborhoods.
-
B.
road in Victoria
A road in Victoria is a designated public or private thoroughfare within the state of Victoria, Australia, used for vehicular and pedestrian travel and managed under local and state transport regulations.
-
C.
road in Sydney
A road in Sydney is a public thoroughfare within the Sydney metropolitan area designed for vehicular and pedestrian traffic, connecting residential, commercial, and recreational locations while integrating with the city's broader transport network.
-
D.
road infrastructure
chosen
Road infrastructure encompasses the physical structures, systems, and facilities—such as roads, bridges, tunnels, signage, and drainage—designed and built to support safe and efficient vehicular and pedestrian transportation.
-
E.
road in South Australia
A road in South Australia is a designated public thoroughfare within the state’s transport network, providing vehicular and pedestrian access between locations under South Australian jurisdiction and standards.
- 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_69f76e44993481908fa75e4c48d0aab3 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.