Triple
T36584514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tūhoe |
E902485
|
entity |
| Predicate | hasTreatySettlementLegislation |
P99458
|
FINISHED |
| Object | Te Urewera Act 2014 |
—
|
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: Te Urewera Act 2014 | Statement: [Tūhoe, hasTreatySettlementLegislation, Te Urewera Act 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTreatySettlementLegislation Context triple: [Tūhoe, hasTreatySettlementLegislation, Te Urewera Act 2014]
-
A.
hasTreatySettlementWith
Indicates the existence of a formal treaty-based agreement or settlement between two parties.
-
B.
treatySettlementInstrument
Indicates that a treaty serves as the formal legal instrument by which a settlement or agreement between parties is established or implemented.
-
C.
establishedByTreatyOrAct
chosen
Indicates that the relationship or entity was formally created, defined, or authorized through a specific treaty or legislative act.
-
D.
hasMainTreaty
Indicates that one entity is the primary or principal treaty associated with another entity.
-
E.
treatyImplemented
Indicates that the terms or provisions of a treaty have been put into effect or carried out in practice between the relevant parties.
- 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_69f76e64d8908190868473959a250b94 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fff59a00a881909b35b799654b3c45 |
completed | May 10, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69fff4d0a2e081909c972189b33d0128 |
completed | May 10, 2026, 3 a.m. |
Created at: May 3, 2026, 4:11 p.m.