Triple
T2368494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waitangi Tribunal |
E46036
|
entity |
| Predicate | claimsType |
P6273
|
FINISHED |
| Object | historical Treaty of Waitangi breaches |
—
|
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 Treaty of Waitangi breaches | Statement: [Waitangi Tribunal, claimsType, historical Treaty of Waitangi breaches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimsType Context triple: [Waitangi Tribunal, claimsType, historical Treaty of Waitangi breaches]
-
A.
attributeClaim
Indicates that one entity asserts or specifies a particular attribute or property about another entity.
-
B.
credentialType
Indicates the specific kind or category of credential associated with an entity or relationship.
-
C.
claimsToBe
Indicates that one entity asserts or declares itself to have a particular identity, role, or property, regardless of whether this assertion is true.
-
D.
aidType
Indicates the type or category of assistance or support being provided in the relationship.
-
E.
typeOfClaim
chosen
Indicates the specific category or nature of a claim being made in relation to an entity or statement.
- 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_69a88a145268819083e2736cb835c696 |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc76bf75c8190b014c3dbfc46bba3 |
completed | March 7, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69abc59b88348190a2d6c08f69974117 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:56 p.m.