Triple
T35614631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hilltops Council |
E1029131
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional local government area |
C65744
|
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: regional local government area Context triple: [Hilltops Council, instanceOf, regional local government area]
-
A.
local government area classification
A local government area classification is a system that categorizes geographic regions based on their administrative governance structures, responsibilities, and jurisdictional boundaries within a country.
-
B.
local government area of Victoria
A local government area of Victoria is an administrative region within the Australian state of Victoria, governed by a local council responsible for providing municipal services, planning, and community facilities to its residents.
-
C.
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.
-
D.
regional district electoral area
A regional district electoral area is a geographically defined subdivision within a regional district used to elect a representative to the district’s governing board, typically encompassing unincorporated or rural communities.
-
E.
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.
- 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_69f76e0709408190bbe322bf1707ef6b |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.