Triple
T33238891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Te Aupōuri |
E850908
|
entity |
| Predicate | hasNeighboringIwi |
P200083
|
FINISHED |
| Object | Ngāti Kuri |
—
|
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: Ngāti Kuri | Statement: [Te Aupōuri, hasNeighboringIwi, Ngāti Kuri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighboringIwi Context triple: [Te Aupōuri, hasNeighboringIwi, Ngāti Kuri]
-
A.
hasNeighbouringWard
Indicates that one ward is directly adjacent to or borders another ward geographically.
-
B.
hasNeighborRelationshipWith
Indicates that one entity is located adjacent to or directly next to another entity, sharing a neighbor relationship.
-
C.
hasNeighboringLGA
Indicates that one local government area is geographically adjacent to or directly borders another local government area.
-
D.
hasNeighboringExclave
Indicates that one entity possesses an exclave that directly borders or is adjacent to an exclave of another entity.
-
E.
hasNeighbouringDivision
Indicates that one division is directly adjacent to and shares a boundary with another division.
- 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_69f34962386c81909ddc3bf9e18ddeb8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff70ecc1a481909571b18d56d982b8 |
completed | May 9, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69ff70322a3c8190837840ea42cd3093 |
completed | May 9, 2026, 5:34 p.m. |
| PDg | Predicate description generation | batch_69ff70ebec7481908d8a4124c8d531df |
completed | May 9, 2026, 5:37 p.m. |
Created at: May 1, 2026, 1:31 a.m.