Triple
T25476386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Moreland |
E638443
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local government area of Victoria |
C50233
|
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: local government area of Victoria Context triple: [City of Moreland, instanceOf, local government area of Victoria]
-
A.
Tasmanian local government area
A Tasmanian local government area is an administrative region within the Australian state of Tasmania, governed by a local council responsible for providing municipal services, planning, and community development.
-
B.
local government area of Western Australia
A local government area of Western Australia is an administrative region governed by a local council responsible for providing municipal services, infrastructure, and community governance within its defined boundaries in the state of Western Australia.
-
C.
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.
-
D.
Queensland local government area
A Queensland local government area is a defined geographic region within the Australian state of Queensland that is administered by a local council responsible for providing municipal services and local governance.
-
E.
group of local government areas
A group of local government areas is a collection of neighboring administrative regions that are organized together for coordinated governance, planning, and service delivery.
- 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_69e75db9b964819096802dcf502e577e |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 2:26 p.m.