Triple
T3323707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Department of Parliamentary Services |
E69859
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Australian government department |
C13652
|
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 department Context triple: [Department of Parliamentary Services, instanceOf, Australian government department]
-
A.
Canadian federal government department
A Canadian federal government department is a primary administrative unit of the Government of Canada responsible for developing, implementing, and managing policies, programs, and services within a specific area of national jurisdiction.
-
B.
British government department
A British government department is an administrative unit of the UK government responsible for developing and implementing public policy and delivering specific services within a defined area of national governance.
-
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.
Canadian government office
A Canadian government office is an administrative unit within federal, provincial, or territorial government that delivers public services, implements policies, and supports the operations of elected and appointed officials in Canada.
-
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. 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_69ad85a1829881908942c14075644d0d |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:11 p.m.