Triple
T16975310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barkly Region |
E411795
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local government area of the Northern Territory |
C38339
|
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 the Northern Territory Context triple: [Barkly Region, instanceOf, local government area of the Northern Territory]
-
A.
Northern Territory electoral division
A Northern Territory electoral division is a geographically defined area within Australia's Northern Territory that elects a representative to the Territory's Legislative Assembly.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
Australian external territory locality
An Australian external territory locality is a defined geographic area within one of Australia’s offshore external territories, recognized for administrative, statistical, or governance purposes.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:31 a.m.