Triple
T25025100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APS |
E626689
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Australian Public Service |
C49699
|
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 Public Service Context triple: [APS, instanceOf, Australian Public Service]
-
A.
Australian Public Service employee
An Australian Public Service employee is a non-political government worker engaged under the Public Service Act to deliver programs, develop policy, and provide services on behalf of the Australian Government.
-
B.
Australian federal government
The Australian federal government is the national governing authority of Australia, comprising the executive, legislative, and judicial branches that administer and enforce laws across the Commonwealth.
-
C.
Australian public office
An Australian public office is an official position within the government or public sector of Australia, established by law or authority, through which an individual exercises public functions, powers, or duties on behalf of the state or community.
-
D.
Australian government agency
An Australian government agency is an official public sector organization established by the Commonwealth or a state/territory government to implement laws, deliver services, and administer specific policy areas within Australia.
-
E.
Australian government department
An Australian government department is a formal administrative unit of the Australian Public Service responsible for implementing federal laws, policies, and programs within a specific portfolio area under the direction of a minister.
- 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:07 a.m.