Triple
T25977531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moriori Claims Settlement Act 2021 |
E645981
|
entity |
| Predicate | typeOfRedress |
P45969
|
FINISHED |
| Object | historical 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: historical redress | Statement: [Moriori Claims Settlement Act 2021, typeOfRedress, historical redress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfRedress Context triple: [Moriori Claims Settlement Act 2021, typeOfRedress, historical redress]
-
A.
reparationsType
chosen
Indicates the specific category or form of reparations involved in a reparative action or obligation between entities.
-
B.
redemptionType
Indicates the manner or method by which something (such as a benefit, reward, or obligation) can be redeemed or fulfilled.
-
C.
typeOfAppeals
Indicates the specific category or kind of appeals associated with or applied to a given case, decision, or legal action.
-
D.
receivedRedress
Indicates that an entity has been given compensation, remedy, or corrective action in response to a prior harm, grievance, or injustice.
-
E.
resolutionType
Indicates the specific manner or category by which an issue, event, or conflict is resolved or brought to a conclusion.
- 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_69e77e8768648190b27bb578f14bcb88 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 22, 2026, 8:52 a.m.