Triple
T17494989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Te Awa Tupua (Whanganui River Claims Settlement) Act 2017 |
E426032
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | settlement legislation |
C3028
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: settlement legislation Context triple: [Te Awa Tupua (Whanganui River Claims Settlement) Act 2017, instanceOf, settlement legislation]
-
A.
settlement policy
Settlement policy is a set of principles and rules that govern how disputes are resolved and agreements are reached, typically outlining procedures, criteria, and terms for negotiating and finalizing settlements.
-
B.
legal settlement
chosen
A legal settlement is an agreement between disputing parties to resolve a legal claim or lawsuit, typically involving negotiated terms such as payment or actions, without proceeding to a final court judgment.
-
C.
settlement type
A settlement type is a classification of human habitation based on characteristics such as size, population density, function, and spatial organization (e.g., village, town, city, metropolis).
-
D.
arbitration legislation
Arbitration legislation is the body of laws and regulations that governs how disputes are resolved through arbitration instead of traditional court litigation, defining procedures, rights, and enforcement of arbitral awards.
-
E.
settlement in Japan
A settlement in Japan is a geographically defined inhabited place, such as a city, town, village, or hamlet, recognized within Japan’s administrative and cultural landscape as a distinct community where people live and interact.
- F. None of above.
Provenance (1 batch)
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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:48 a.m.