Triple
T9478573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tenancy Tribunal of New Zealand |
E228575
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | dispute resolution body |
C2308
|
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: dispute resolution body Context triple: [Tenancy Tribunal of New Zealand, instanceOf, dispute resolution body]
-
A.
tax dispute resolution body
A tax dispute resolution body is an independent authority or tribunal that reviews and adjudicates disagreements between taxpayers and tax authorities over assessments, liabilities, or interpretations of tax law.
-
B.
specialized arbitration body
A specialized arbitration body is an independent, expert tribunal established to resolve disputes within a particular field or industry through binding or non-binding arbitral decisions.
-
C.
quasi‑judicial body
chosen
A quasi-judicial body is an administrative or regulatory entity that has powers and procedures resembling those of a court, enabling it to interpret laws, conduct hearings, and make binding decisions or recommendations in specific areas of public or private disputes.
-
D.
alternative dispute resolution program
An alternative dispute resolution program is a structured process that uses methods such as mediation, arbitration, or negotiation to help parties resolve conflicts outside of traditional court litigation.
-
E.
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.
- 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_69ca84730a5081908de282651019bf2f |
completed | March 30, 2026, 2:10 p.m. |
Created at: March 30, 2026, 7:54 p.m.