Triple
T1397850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Public Service headquarters |
E30708
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative headquarters |
C400
|
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: administrative headquarters Context triple: [Australian Public Service headquarters, instanceOf, administrative headquarters]
-
A.
headquarters
chosen
The headquarters is the primary location where an organization’s central management, strategic decision-making, and key administrative functions are coordinated and controlled.
-
B.
headquarters agreement
A headquarters agreement is a formal treaty or contract between an international organization and a host state that defines the legal status, privileges, immunities, and operational conditions of the organization’s headquarters within that state.
-
C.
public administration body
A public administration body is an organization within the public sector responsible for implementing laws, delivering public services, and managing governmental policies and resources on behalf of the state and its citizens.
-
D.
colonial office
A colonial office is a governmental department or administrative body responsible for managing and overseeing the affairs, policies, and governance of a colony or group of colonies on behalf of a colonial power.
-
E.
public administration
Public administration is the field and practice of implementing government policies, managing public programs, and coordinating resources and personnel to serve the public interest and promote effective governance.
- 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_69a498fd4e408190bd73eca30ea9754c |
completed | March 1, 2026, 7:52 p.m. |
Created at: March 1, 2026, 7:59 p.m.