Triple
T25340920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dequetteville Terrace |
E635409
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | street in Adelaide |
C44722
|
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: street in Adelaide Context triple: [Dequetteville Terrace, instanceOf, street in Adelaide]
-
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 South Australia
chosen
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 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.
Melbourne tram route
A Melbourne tram route is a designated public transport line within Melbourne’s tram network, defined by a specific number or name, a fixed path along city streets and suburbs, and scheduled services connecting key destinations.
-
E.
street
A street is a public thoroughfare in an urban or suburban area, typically bordered by buildings, that facilitates vehicular and pedestrian movement and often supports various social and commercial activities.
- 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
Created at: April 21, 2026, 1:32 p.m.