Triple
T36447496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngāti Raukawa ki te Tonga |
E897915
|
entity |
| Predicate | hasTreatyInterest |
P201350
|
FINISHED |
| Object | Treaty of Waitangi settlements |
—
|
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: Treaty of Waitangi settlements | Statement: [Ngāti Raukawa ki te Tonga, hasTreatyInterest, Treaty of Waitangi settlements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTreatyInterest Context triple: [Ngāti Raukawa ki te Tonga, hasTreatyInterest, Treaty of Waitangi settlements]
-
A.
isInTreaty
Indicates that two or more entities are formally bound together by the terms of a treaty or formal agreement.
-
B.
hasTreatyRight
Indicates that an entity holds a legally recognized right or entitlement established by a formal treaty with another party.
-
C.
hasMainTreaty
Indicates that one entity is the primary or principal treaty associated with another entity.
-
D.
hasTreatySettlementWith
Indicates the existence of a formal treaty-based agreement or settlement between two parties.
-
E.
treatyFeature
Indicates that one entity is a characteristic, provision, or specific element that forms part of a treaty.
- 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_69f76e5720b481908f8177ac24a7560b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffecdcbac4819093b725a7dbe0e61b |
completed | May 10, 2026, 2:26 a.m. |
| PD | Predicate disambiguation | batch_69ffec3633288190adbbd84e277708dc |
completed | May 10, 2026, 2:23 a.m. |
| PDg | Predicate description generation | batch_69ffecdbe62081909f901e7d4db69d60 |
completed | May 10, 2026, 2:26 a.m. |
Created at: May 3, 2026, 4:10 p.m.