Triple
T16408068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngāti Ruanui |
E398486
|
entity |
| Predicate | settledTreatyClaimsIn |
P123311
|
FINISHED |
| Object | early 2000s |
—
|
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: early 2000s | Statement: [Ngāti Ruanui, settledTreatyClaimsIn, early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settledTreatyClaimsIn Context triple: [Ngāti Ruanui, settledTreatyClaimsIn, early 2000s]
-
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.
establishedByTreatyOrAct
Indicates that the relationship or entity was formally created, defined, or authorized through a specific treaty or legislative act.
-
C.
historicalSovereigntyClaim
Indicates a relationship where an entity asserts that it held sovereign authority over another entity or territory at some point in the past.
-
D.
settledAs
Indicates that one entity has been resolved, finalized, or agreed upon in the form or status of another entity.
-
E.
treatyRights
Indicates that there exist rights, obligations, or privileges established by a formal treaty between parties.
- F. None of above. chosen
Provenance (4 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32870e44c8190aae7bc6e6022ceb7 |
completed | April 18, 2026, 6:45 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:09 a.m.