Triple
T26480981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goulburn Valley Highway |
E664682
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road in Victoria |
C51630
|
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 in Victoria Context triple: [Goulburn Valley Highway, instanceOf, road in Victoria]
-
A.
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.
-
B.
road in Queensland
A road in Queensland is a designated vehicular thoroughfare within the Australian state of Queensland, ranging from major highways to local streets, that facilitates transportation, access, and connectivity between urban, regional, and remote areas.
-
C.
road in Western Australia
A road in Western Australia is a constructed vehicular route within the state’s vast and often remote landscape, designed to connect towns, cities, mining regions, and tourist destinations under local, state, or federal management.
-
D.
state rural road in New South Wales
A state rural road in New South Wales is a government-designated roadway outside urban areas that connects regional towns, agricultural districts, and key rural facilities to the broader state road network.
-
E.
road in Virginia
A road in Virginia is a designated vehicular travelway within the Commonwealth of Virginia that facilitates transportation, access, and connectivity between locations while adhering to state and local regulations and infrastructure standards.
- 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_69ee883bc85481909885f92415cbce33 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 27, 2026, 12:27 a.m.