Triple
T21910058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APS officers |
E541036
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Australian Public Service employee |
C45503
|
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 employee Context triple: [APS officers, instanceOf, Australian Public Service employee]
-
A.
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.
-
B.
Australian federal politician
An Australian federal politician is an elected representative who serves in the Parliament of Australia, participating in national lawmaking, governance, and oversight on behalf of their constituents.
-
C.
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.
-
D.
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.
-
E.
British civil servant
A British civil servant is a non-political government employee who supports the administration and implementation of public policy within the United Kingdom’s civil service.
- 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_69e0c47c4b9c8190a5586a75f5f36453 |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 7:40 p.m.