Triple
T26164681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | electorate of Kurrajong |
E654215
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Australian Capital Territory Legislative Assembly electorate |
C1141
|
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: Australian Capital Territory Legislative Assembly electorate Context triple: [electorate of Kurrajong, instanceOf, Australian Capital Territory Legislative Assembly electorate]
-
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.
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.
former New South Wales state electoral district
A former New South Wales state electoral district is a geographically defined constituency that once elected a representative to the New South Wales Legislative Assembly but has since been abolished or replaced through electoral redistribution.
-
D.
Act of the Australian Capital Territory
An Act of the Australian Capital Territory is a law formally enacted by the ACT Legislative Assembly that governs matters within the Territory’s jurisdiction.
-
E.
electoral district
chosen
An electoral district is a geographically defined area represented by an elected official, within which eligible voters choose their representatives in a legislative body.
- 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
Created at: April 26, 2026, 8:32 p.m.