Triple
T32111560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Te Rūnanga-Ā-Iwi O Ngāpuhi |
E820129
|
entity |
| Predicate | representsInTreatyMatters |
P5763
|
FINISHED |
| Object | Ngāpuhi iwi |
—
|
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āpuhi iwi | Statement: [Te Rūnanga-Ā-Iwi O Ngāpuhi, representsInTreatyMatters, Ngāpuhi iwi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsInTreatyMatters Context triple: [Te Rūnanga-Ā-Iwi O Ngāpuhi, representsInTreatyMatters, Ngāpuhi iwi]
-
A.
roleInTreaties
Indicates the specific capacity, function, or position an entity holds within the context of one or more treaties.
-
B.
relatedToTreaty
chosen
Indicates that there exists a connection, association, or relevance between an entity and a specific treaty or treaties.
-
C.
linkedToTreaty
Indicates that an entity has a formal connection or association with a specific treaty, such as being established by, governed by, or otherwise related to that treaty.
-
D.
treatyOrLegalIssue
Indicates a formal agreement, dispute, or matter governed by treaties or legal frameworks between parties.
-
E.
treatyMention
Indicates that a treaty is referenced or mentioned in relation to the associated entities or context.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe779248c081909f0ed1a2a0df23db |
completed | May 8, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69fe76eaf6d48190998bc7168749cc42 |
completed | May 8, 2026, 11:51 p.m. |
Created at: May 1, 2026, 12:27 a.m.