Triple
T27358907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adelaide Street (Brisbane) |
E685763
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road in Brisbane |
C52753
|
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 Brisbane Context triple: [Adelaide Street (Brisbane), instanceOf, road in Brisbane]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
Created at: April 27, 2026, 11:52 a.m.