Triple
T9493640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remuneration Authority of New Zealand |
E228951
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | remuneration-setting authority |
C14004
|
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: remuneration-setting authority Context triple: [Remuneration Authority of New Zealand, instanceOf, remuneration-setting authority]
-
A.
appointing authority
An appointing authority is an individual or entity legally empowered to select, hire, promote, or otherwise make official personnel decisions for positions within an organization or governmental body.
-
B.
regulatory authority
A regulatory authority is an official body empowered by law to create, implement, and enforce rules and standards within a specific domain to protect public interests and ensure compliance.
-
C.
rule‑making committee
A rule‑making committee is a group formally tasked with developing, reviewing, and approving rules or regulations that govern the behavior, procedures, or operations of an organization or system.
-
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.
administrative authority
chosen
An administrative authority is an organization or body empowered by law or policy to implement, manage, and enforce rules, regulations, and public administration decisions within a defined jurisdiction.
- 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.