Triple
T27250228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunraysia Highway |
E687464
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road in Victoria, Australia |
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, Australia Context triple: [Sunraysia Highway, instanceOf, road in Victoria, Australia]
-
A.
road in Victoria
chosen
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69ef35567e808190a94458cd44ebff0c |
completed | April 27, 2026, 10:07 a.m. |
Created at: April 27, 2026, 10:44 a.m.