Triple
T30796176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canterbury Earthquake Recovery Authority |
E784234
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | New Zealand Crown agency |
C33010
|
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: New Zealand Crown agency Context triple: [Canterbury Earthquake Recovery Authority, instanceOf, New Zealand Crown agency]
-
A.
New Zealand Crown entity
chosen
A New Zealand Crown entity is an organization that is part of the state sector but operates at arm’s length from ministers, performing public functions or services under specific statutory or government mandates.
-
B.
New Zealand public service department
A New Zealand public service department is a central government organization established by statute or the Public Service Act to deliver public services, implement government policy, and support ministers in their executive functions within New Zealand’s state sector.
-
C.
New Zealand organisation
A New Zealand organisation is a formally structured group or entity that operates within or is primarily associated with New Zealand to pursue specific goals, activities, or services.
-
D.
Government of New Zealand
The Government of New Zealand is the constitutional monarchy and parliamentary democracy that exercises executive authority, creates and enforces laws, and administers public services within New Zealand.
-
E.
New Zealand company
A New Zealand company is a legally incorporated business entity formed under New Zealand law, typically registered with the Companies Office and subject to local governance, tax, and reporting requirements.
- 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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:42 p.m.