Triple
T9493639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remuneration Authority of New Zealand |
E228951
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | independent statutory body |
C1300
|
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: independent statutory body Context triple: [Remuneration Authority of New Zealand, instanceOf, independent statutory body]
-
A.
independent organization
An independent organization is an entity that operates autonomously from external control or affiliation, making its own decisions, policies, and governance.
-
B.
independent administrative authority
chosen
An independent administrative authority is a public body, separate from the traditional executive hierarchy, endowed with regulatory or supervisory powers and functional autonomy to ensure impartial decision-making in a specific sector or policy area.
-
C.
advisory body
An advisory body is a group of appointed or elected individuals that provides expert guidance, recommendations, and informed opinions to decision-makers without having formal authority to implement decisions.
-
D.
governing body
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
E.
non-departmental public body
A non-departmental public body is an organization that operates at arm’s length from government departments to carry out public functions, often with its own board and a degree of operational independence while remaining publicly accountable.
- 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_69ca847424f081908180305555139f7a |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 7:56 p.m.