Triple
T34556008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District Court of Western Australia |
E887204
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | court in Western Australia |
C61404
|
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: court in Western Australia Context triple: [District Court of Western Australia, instanceOf, court in Western Australia]
-
A.
court of New South Wales
The court of New South Wales is a judicial body within the Australian state of New South Wales responsible for interpreting and applying the law, resolving disputes, and administering justice according to state and federal legislation.
-
B.
region of Western Australia
A region of Western Australia is a defined geographic area within the state used for administrative, economic, cultural, and planning purposes, often characterized by shared environmental features and community identity.
-
C.
road in Western Australia
A road in Western Australia is a constructed vehicular route within the state’s vast and often remote landscape, designed to connect towns, cities, mining regions, and tourist destinations under local, state, or federal management.
-
D.
New Zealand court
A New Zealand court is a judicial body established under New Zealand law that interprets and applies legislation, resolves disputes, and administers justice within its jurisdiction.
-
E.
South Australian legislation
South Australian legislation is the body of laws enacted by the Parliament of South Australia that governs legal rights, responsibilities, and regulatory frameworks within the state.
- 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_69f349cff89081908f91e0b064f4833e |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:02 a.m.