Triple
T20587943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngāti Tama |
E505835
|
entity |
| Predicate | treatySettlementIncludes |
P138561
|
FINISHED |
| Object | cultural redress |
—
|
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: cultural redress | Statement: [Ngāti Tama, treatySettlementIncludes, cultural redress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatySettlementIncludes Context triple: [Ngāti Tama, treatySettlementIncludes, cultural redress]
-
A.
treatySettlementInstrument
Indicates that a treaty serves as the formal legal instrument by which a settlement or agreement between parties is established or implemented.
-
B.
hasTreatySettlementWith
Indicates the existence of a formal treaty-based agreement or settlement between two parties.
-
C.
resultOfTreaties
chosen
Indicates that something exists, occurs, or holds true as a consequence or outcome of one or more treaties.
-
D.
treatySettlementYear
Indicates the year in which a treaty was formally settled or concluded.
-
E.
treatyScope
Indicates the range, subject matter, or extent of issues and obligations that a treaty covers or applies to.
- 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_69e0b4b9669c8190b8e81fc72817d42c |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a9790cc08190b48949834cd421d2 |
completed | April 20, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:40 a.m.