Triple
T32224401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngāpuhi |
E823154
|
entity |
| Predicate | governanceBodyType |
P158668
|
FINISHED |
| Object | mandated iwi authority |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: mandated iwi authority | Statement: [Ngāpuhi, governanceBodyType, mandated iwi authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governanceBodyType Context triple: [Ngāpuhi, governanceBodyType, mandated iwi authority]
-
A.
governingBodyOfType
Indicates that an entity serves as the official governing body for another entity of a specified type or category.
-
B.
organizationTypeOfGoverningBody
chosen
Indicates the type or classification of the organization that serves as the governing body for an entity.
-
C.
governmentBodyType
Indicates the classification or category of a governmental organization based on its structural or functional role.
-
D.
governingBody2
Indicates that an entity serves as the official authority or administrative body responsible for overseeing, managing, or regulating another entity.
-
E.
governingBodyId
Indicates the entity that serves as the official governing body responsible for overseeing or managing another entity.
- F. None of above.
Provenance (3 batches)
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_69f3490b4f948190b99e4f999f5be25f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a003ffb548081908ba64fd2b570f42f |
completed | May 10, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_6a003fcecf788190a13dff38b9de3414 |
completed | May 10, 2026, 8:20 a.m. |
Created at: May 1, 2026, 12:38 a.m.