Triple
T32644048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngāti Hauiti |
E834553
|
entity |
| Predicate | iwiAuthorityLocation |
P174760
|
FINISHED |
| Object | Rātā |
—
|
NE NERFINISHED |
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: Rātā | Statement: [Ngāti Hauiti, iwiAuthorityLocation, Rātā]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: iwiAuthorityLocation Context triple: [Ngāti Hauiti, iwiAuthorityLocation, Rātā]
-
A.
iwiAuthorityType
Indicates the specific type or category of authority held by an iwi within a given context or governance framework.
-
B.
iwiAuthorityEstablished
Indicates that an iwi’s formal authority or governance over a particular area, resource, or matter has been officially recognized or established.
-
C.
registrationAuthorityLocatedIn
Indicates that the authority responsible for registration is situated within a specified geographic or jurisdictional location.
-
D.
localIwi
Indicates that an entity is associated with, belongs to, or is located within the area of a particular local iwi (tribe).
-
E.
hasLocationRole
Indicates that an entity holds or plays a specific role in relation to a particular location (e.g., origin, destination, storage site, or operational area).
- F. None of above. chosen
Provenance (4 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_69f3492e773c81908afc10651e46cad3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c7e32ec08190b74856937c4a9fc3 |
completed | May 3, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c77500a08190b2bdeca33bd2ac08 |
completed | May 3, 2026, 3:56 a.m. |
Created at: May 1, 2026, 1:07 a.m.