Triple
T26783863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russell |
E670324
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | suburb of Canberra |
C50347
|
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: suburb of Canberra Context triple: [Russell, instanceOf, suburb of Canberra]
-
A.
suburb district of Canberra
chosen
A suburb district of Canberra is a defined residential and mixed-use area within the Canberra metropolitan region, characterized by its own local amenities, community identity, and governance within the broader Australian Capital Territory.
-
B.
district of Canberra
A district of Canberra is an administrative division of the Australian Capital Territory that groups together multiple suburbs for local governance, planning, and service delivery within the Canberra metropolitan area.
-
C.
suburb of Melbourne
A suburb of Melbourne is a defined residential or mixed-use area located within the greater Melbourne metropolitan region, characterized by its own local amenities, community identity, and governance under a local council.
-
D.
suburb of Wellington
A suburb of Wellington is a residential or mixed-use area located within the greater Wellington metropolitan region, typically characterized by local amenities, community services, and transport links to the central city.
-
E.
region of Victoria
A region of Victoria is a defined geographic area within the state of Victoria, Australia, characterized by shared administrative boundaries, economic activities, and cultural or environmental features.
- 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_69eeb31d45f8819089f52ebdbc556218 |
completed | April 27, 2026, 12:51 a.m. |
Created at: April 27, 2026, 4:11 a.m.