Triple
T37293894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngāti Pūkenga |
E925745
|
entity |
| Predicate | hasAncestralRightsIn |
P117980
|
FINISHED |
| Object | Bay of Plenty region |
—
|
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: Bay of Plenty region | Statement: [Ngāti Pūkenga, hasAncestralRightsIn, Bay of Plenty region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAncestralRightsIn Context triple: [Ngāti Pūkenga, hasAncestralRightsIn, Bay of Plenty region]
-
A.
hasHereditaryRights
Indicates that one entity possesses rights or privileges that are passed down through family lineage or inheritance from another entity.
-
B.
hasAncestralLand
Indicates that an entity possesses land inherited from its ancestors or traditionally associated with its lineage.
-
C.
hasAncestralLandsOf
Indicates that one entity possesses or is traditionally associated with the ancestral lands belonging to another entity.
-
D.
hasAncestralResidence
Indicates that an entity has a residence or dwelling place that belonged to or was established by its ancestors.
-
E.
hasTraditionalRights
chosen
Indicates that an entity possesses customary or historically established rights or privileges in relation to another entity or resource.
- 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_69f76eb0f86c819098dee07393e69ec3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: May 3, 2026, 4:16 p.m.