Triple
T13546292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Coordination Office |
E323520
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Australian government body |
C15698
|
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 government body Context triple: [Space Coordination Office, instanceOf, Australian government body]
-
A.
Australian government agency
chosen
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.
-
B.
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.
-
C.
Australian company
An Australian company is a legally registered business entity that operates in or from Australia, subject to Australian corporate, tax, and regulatory frameworks.
-
D.
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.
-
E.
British government ministry
A British government ministry is a central department of the UK government, headed by a minister, responsible for developing and implementing public policy and administering specific areas of national 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:45 p.m.